Setup
Where Origin Stores Claude Code Memory
Find the local files Origin writes when Claude Code captures memories, handoffs, and distilled pages.
Article packet
Workflows
Claude Code users checking where memory lives on disk
5 min read
01
Origin writes readable artifacts under ~/.origin instead of hiding memory inside a chat profile.
02
Distilled pages live under ~/.origin/pages and session handoffs live under ~/.origin/sessions.
03
Readable pages and session handoffs are versioned in ~/.origin/.git.
01
Quick answer
Origin stores its local runtime and readable artifacts under ~/.origin. That is separate from Claude Code's own CLAUDE.md and auto-memory systems: Claude Code runs the plugin and calls MCP tools, while Origin's daemon owns the local memory store.
Origin's answer is deliberately boring: the memory layer is local. Memories live in the daemon database, while pages, handoffs, project status, and local git history are exposed as readable artifacts.
02
When this problem appears
This question usually comes up after a user installs the Claude Code plugin and wants to know whether memories are trapped inside Claude Code, stored in the cloud, or written somewhere they can inspect.
03
Inspect the local artifacts
After setup, use the filesystem and CLI to confirm what Origin wrote.
- Check ~/.origin/pages for distilled Markdown pages.
- Check ~/.origin/sessions for handoffs and project status.
- Check ~/.origin/db on macOS or Linux for the convenience symlink to the libSQL store.
- Run ~/.origin/bin/origin status to verify the daemon.
- Inspect ~/.origin/.git when you need history for readable artifact writes.
Local artifact checks
ls ~/.origin
ls ~/.origin/pages
ls ~/.origin/sessions
~/.origin/bin/origin status
git -C ~/.origin log --oneline -504
What to check next
Do not edit the database directly. MCP memories live in the daemon DB; distilled pages and session handoffs are the readable projection. Use Origin commands and tools for memory writes, review, distill, and delete.
Try the local memory loop
Install Origin, connect your AI client, and verify that capture, recall, and handoff work on your machine.
FAQ