# Memory Continue

Resume prior work by rebuilding context from the Basic Memory graph via memory:// URLs...

- Repository: https://github.com/basicmachines-co/basic-memory (4440 stars)
- Category: Engineering
- License: AGPL-3.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add basicmachines-co/basic-memory --skill memory-continue -g -a claude-code -y`
Codex: `npx skills add basicmachines-co/basic-memory --skill memory-continue -g -a codex -y`
Cursor: `npx skills add basicmachines-co/basic-memory --skill memory-continue -g -a cursor -y`
Gemini CLI: `npx skills add basicmachines-co/basic-memory --skill memory-continue -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add basicmachines-co/basic-memory`

## Description

Resume prior work by rebuilding context from the Basic Memory graph via memory:// URLs, recent activity, and search. Use at session start or on 'continue with...', 'back to...', 'where were we?

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Memory Continue

Resume previous work by reconstructing context from the Basic Memory knowledge graph, so the assistant can pick up across sessions instead of starting cold.

## Project scope

If the project is unknown, discover it with `bm_project(command="list")`.
Pass a nonempty `project` on every note, folder, context and schema call, even
with one project or a qualified `memory://` URL. Use the chosen project's name,
`workspace/project`, or external ID; `<project>` below is a placeholder for it.
Recent activity also requires `project`. Search accepts `project` for one
project, `projects` for selected projects, or `all_projects=True` explicitly.
Discovery and bundled manuals need no project. Keep the same scope when following
returned paths, paginating, or recovering from a refusal.

## When to Use

- Starting a new session and you need to pick up where you left off
- The user references earlier work: "continue with...", "back to...", "where were we on...?"
- You need context about an ongoing project or spec
- The user asks about something discussed in a previous conversation
- You're working on a task that spans multiple sessions

## Building Context

### 1. Identify What to Continue

If it's unclear, ask:
- What topic or project should you resume?
- What since matters?
- Any specific aspect to focus on?

### 2. Gather Context with MCP Tools

**Known topic, use `bm_context`.** Navigate the graph from a starting point, following relations outward:

```python
bm_context(
    identifier="memory://topic-or-note-name",
    depth=2,           # how many relation hops to follow
    since="7d",        # only include changes in this window
    project="<project>",
)
```

**No clear starting point, use `bm_project(command="recent", project="<project>")`.** See what's changed and let it surface the thread:

```python
bm_project(command="recent", since="3d", project="<project>")
```

The rest: https://github.com/basicmachines-co/basic-memory/blob/HEAD/skills/memory-continue/SKILL.md