memory-continue — Claude Code skill: resume work across sessions
This skill rebuilds context from the Basic Memory graph so your assistant picks up previous work instead of starting cold.
npx skills add basicmachines-co/basic-memory --skill memory-continue -a claude-codeWhat memory-continue does
Reach for it at the start of a session, or when you say something like “continue with the refactor” and expect the agent to know what that means. The skill reconstructs the thread from notes stored in Basic Memory.
It walks the knowledge graph with MCP tools. bm_context follows relations outward from a starting note at a chosen depth, bm_project(command="recent") surfaces what changed lately, bm_search finds candidate notes by keyword, and bm_read opens one in full or just a slice. Time windows come as plain words: "today", "3d", "2 weeks", "1 month".
None of those calls work without the Basic Memory MCP server configured, since the skill has nothing else to read from. Project names differ per user, so run bm_project(command="list") first and scope a memory:// URL with a project prefix when you keep several, as in memory://research/papers/crdt.
What it helps with
- rebuild session context without retelling it yourself
- locate notes on a topic when the filename is long gone
- pull related notes around a spec or project
- see what changed over the past few days
- continue a task that spans several sessions
Example prompts for the agent
- Continue work on SPEC-24 and pull the context from memory
- Where did we leave the Postgres migration?
- Go back to the async client refactor and show me the last week of changes
How to install memory-continue
1Skills CLI (Vercel)
npx skills add basicmachines-co/basic-memory --skill memory-continue -a claude-code2Manually: put the files in place
~/.claude/skills/memory-continue/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/memory-continue/
1Skills CLI (Vercel)
npx skills add basicmachines-co/basic-memory --skill memory-continue -a codex2Manually: put the files in place
.agents/skills/memory-continue/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add basicmachines-co/basic-memory --skill memory-continue -a cursor2Manually: put the files in place
.cursor/skills/memory-continue/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install basicmachines-co/basic-memory memory-continue2Manually: put the files in place
.github/skills/memory-continue/SKILL.md1Skills CLI (Vercel)
npx skills add basicmachines-co/basic-memory --skill memory-continue -a gemini-cli2Platform CLI
gemini skills install https://github.com/basicmachines-co/basic-memory --path skills/memory-continueManually: put the files in place
.devin/skills/memory-continue/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add basicmachines-co/basic-memory --skill memory-continue -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about memory-continue
How do I install memory-continue in Claude Code?
Run npx skills add basicmachines-co/basic-memory --skill memory-continue -a claude-code. The skill lands at ~/.claude/skills/memory-continue/SKILL.md.
What does memory-continue do?
It gathers earlier work from the Basic Memory graph — searching notes, following their relations, listing recent changes — so the assistant resumes where you left off.
What does the skill need to run?
A configured Basic Memory MCP server. The skill calls its tools bm_context, bm_search, bm_read and bm_project, and without the server those calls fail.