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:

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:

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