القائمة
Manually upload the persistent memory database to your self-hosted dashboard. Useful after directly running add-fact or add-knowledge — for normal session work, /remember already auto-pushes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Download the persistent memory database from your self-hosted dashboard into the current repo. Use after cloning a repo on a new machine to restore accumulated sessions, knowledge, facts, and embeddings for RAG/context.
Save the current work session to persistent memory for future context. Summarizes accomplishments, tracks files modified, and stores learnings for cross-session continuity.
Interactive TUI knowledge graph viewer for the persistent memory database.
Show token economics comparing usage with turbo-search vs without. Demonstrates actual savings from search-first approach.
Index the current project for optimized search with QMD semantic search and fast file suggestions. Run this when entering a new codebase or after significant changes. Saves 60-80% tokens on exploration tasks.
View statistics and recent entries from the persistent memory database. Shows session count, knowledge areas, facts, and recent activity.
| name | push |
| description | Manually upload the persistent memory database to your self-hosted dashboard. Useful after directly running add-fact or add-knowledge — for normal session work, /remember already auto-pushes. |
Send the current repo's .claude-memory/memory.db to your self-hosted Fly.io dashboard. Slug is derived from git remote get-url origin, so it lands on the right per-repo storage automatically.
When the user invokes /push, run:
PLUGIN_DIR="${PLUGIN_DIR:-$HOME/claude-turbo-search}"
MEMORY_SCRIPT="$PLUGIN_DIR/memory/memory-db.sh"
"$MEMORY_SCRIPT" push
Happy path:
Pushed .../memory.db to https://<dashboard>/api/repos/<slug>/push
Tell the user the dashboard now reflects this push.
No config — message will be:
no sync remote configured. run `memorydb config set --remote URL --token TOKEN`
Tell the user how to configure it.
No local DB — message will be:
no memory database at <path> — nothing to push
Suggest running /remember first (which creates the DB if needed).
add-fact, add-knowledge, or consolidate directly via memory-db.sh doesn't trigger an auto-push. Use /push to sync./remember./remember — that skill auto-pushes already./remember handle pushes at the natural session boundary./pull — the inverse operation (download from dashboard)./remember — auto-pushes after saving the session.web/README.md — full architecture.