Resume prior work by rebuilding context from the Basic Memory knowledge graph — pick up where you left off using memory:// URLs, recent activity, and search. Use when starting a session or when the user says 'continue with...', 'back to...', or 'where were we?'

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. 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 timeframe matters? Any specific aspect to focus on? 2. Gather Context with MCP Tools Known topic — use build context . Navigate the graph from a starting point, following relations outward: No clear starting point — use recent activity . See what's changed and let it surface the thread: Looking for something specific — use search notes . Find candidate notes by keyword: 3. Read the Key Notes Once you've identified the relevant notes, read them in full: 4. Present Context to the User Summarize what you found, incrementally: Current state of the work Recent changes or progress Open items and next steps Related context that might help Memory URL Reference build context and read note both accept memory:// URLs, which address notes by permalink and support wildcards for gathering groups of notes. Use a specific note URL to anchor on one starting point; use a wildcard to pull in a whole folder or family of related notes at once. Timeframe Reference build context and recent activity accept natural language timeframes: Timeframe Meaning "today" Current day "yesterday" Previous day "3d" or "3 days" Last 3 days "1 week" or "7d" Last week "2 weeks" Last 2 weeks "1 month" Last month Scenario Playbooks Resuming a Spec or Project Then summarize: the goals, what's completed, what's pending, and any blockers or open decisions. Continuing General Work Then list the modified notes with brief descriptions and ask which thread to dive into. Following Up on a Topic Then present the full picture — the note plus its connected context. Project Discovery Project names are user specific. To discover what's available before scoping a search or memory:// URL: In multi project setups, prefix a memory:// URL with the project name (e.g. memory://research/papers/crdt ) to scope it. Guidelines 1. Start broad, then narrow. Get an overview with recent activity or a wildcard build context , then drill into specific notes. 2. Present incrementally. Share what you find as you go rather than holding everything until the end. 3. Follow relations. The graph's connections are the point — build context with depth surfaces context you wouldn't find by reading one note. 4. Check multiple projects. Specs may live separately from implementation notes; discover projects with list memory projects . 5. Confirm understanding. Verify the reconstructed context is what the user actually needs before acting on it. 6. Capture new progress. As the resumed work advances, write it back to the graph (see the memory notes skill) so the next session can continue too.

memory-continue