メニュー
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.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/iagocavalcante/claude-turbo-search --skill pullコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
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.
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.
SKILL.md を表示中
SOC 職業分類に基づく
| name | pull |
| description | 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. |
Restore the per-repo memory.db from your self-hosted Fly.io dashboard. The slug is computed from git remote get-url origin, so the same GitHub URL → same data on any machine. No per-repo config needed beyond the global memory-db.sh config set you ran once.
When the user invokes /pull, run:
PLUGIN_DIR="${PLUGIN_DIR:-$HOME/claude-turbo-search}"
MEMORY_SCRIPT="$PLUGIN_DIR/memory/memory-db.sh"
# Pass through any flags the user provided (e.g. --force).
"$MEMORY_SCRIPT" pull "$@"
Happy path (fresh clone, no local DB yet):
Pulled https://<dashboard>/api/repos/<slug>/db -> .claude-memory/memory.db
Then suggest the user run /memory-stats to see what was restored, and /memory-stats search <query> to retrieve specific context.
No config — message will be:
no sync remote configured. run `memorydb config set --remote URL --token TOKEN`
Tell the user how to configure it. Example:
"$MEMORY_SCRIPT" config set --remote https://your-app.fly.dev --token <token>
Nothing on remote — message will be:
no database for this repo on the remote — has it been pushed yet?
Explain that this is normal for a repo that's never been pushed to the dashboard before. Suggest creating memory locally with /remember (which auto-pushes when configured).
Existing local DB without --force — message will be:
local memory.db already exists at <path> (<N> bytes). pass --force to overwrite
Tell the user that pull refuses to clobber non-empty local memory by default. If they really want to overwrite, run /pull --force. Note that there's no merge across machines in v1 — last-write-wins.
.claude-memory/memory.db got mangled, pull from remote to recover./remember-ed something on a laptop and want it on a desktop. (Caveat: only works one-way; pulling discards any unique local memory.)/remember auto-pushes after each session, so the dashboard stays current without manual pulls./memory-stats first to see what's local./push — the inverse operation (manual push without a /remember).web/README.md — full architecture and operating notes.