Workflow
Daily Workflow
Start with context, capture what matters, recall when needed, and hand off before context goes cold.
At a glance
01
Start with /brief in Claude Code or context in MCP clients.
02
Capture durable facts during work; close real sessions with /handoff.
01
Start with context
Start a real work session with /brief in Claude Code or context in another MCP client. Origin returns project facts, recent handoffs, decisions, and distilled pages.
If setup is not done yet, use /init in Claude Code. For other MCP clients, run npx -y @7xuanlu/origin setup before adding the MCP connector.
Session start
Claude Code: /brief
MCP tool: context02
Capture only durable knowledge
Use /capture for knowledge that should survive the current chat: decisions, lessons, gotchas, project constraints, preferences, and facts future agents would otherwise rediscover.
Keep each capture atomic. One idea per memory is easier to search, merge, correct, and cite later.
- Good: We chose local memory because this project needs local search without model setup.
- Good: Origin is AI work memory because it carries context across sessions, tools, and time.
- Skip: command output, temporary todos, filler, and facts the repo can trivially derive.
Claude Code
/capture <one durable thing, including why it matters>03
Recall when history matters
Use /recall when the agent needs a specific thread of past context. This is better than asking the assistant to guess from the current chat.
Specific recall queries work better than broad ones. Name the project, decision, person, feature, or failure mode you care about.
Claude Code
/recall origin website docs decisions04
End with a handoff
/handoff is the closing ritual. It writes a session log, updates project status, and captures decisions, lessons, gotchas, and open threads before the session disappears into chat history.
The next session can start from that handoff instead of rebuilding the situation from memory.
Claude Code
/handoff05
Maintain memory when it grows
/review is for deep audits. /distill turns related memories into wiki pages.
Use them after meaningful project work, before a new phase, or when recall starts surfacing repeated or stale context.
- /review captures: walk unconfirmed memories when you want the full queue.
- /review revisions: accept or dismiss pending memory revisions.
- /distill: synthesize related memories into readable pages.
- /read: preview a distilled page without leaving the agent session.
Next
Core Concepts
Understand the pieces behind Origin: memories, sessions, handoffs, pages, the daemon, MCP, Markdown, and the local index.
Read next