Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From claude-turbo-search
Downloads per-repo memory.db from self-hosted Fly.io dashboard into current repo. Restores accumulated sessions, knowledge, facts, and RAG embeddings after cloning on new machine.
npx claudepluginhub iagocavalcante/claude-turbo-search --plugin claude-turbo-searchHow this skill is triggered — by the user, by Claude, or both
Slash command
/claude-turbo-search:pullThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
Manually pushes repo's .claude-memory/memory.db to self-hosted Fly.io dashboard via git-derived slug. Use after direct memory edits like add-fact or add-knowledge; /remember auto-pushes normally.
Explains how claude-mem captures observations, injects context, and where data is stored locally.
Manages a multi-layered knowledge system: save, organize, sync, deduplicate, and retrieve across local files, MCP memory, vector stores, and Git repos.
Share bugs, ideas, or general feedback.
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.