Backup

Backup and Migration

Back up Origin's readable artifacts and daemon data together, then verify the restored runtime before trusting recall.

Qi-Xuan LuUpdated Jun 1, 20265 min read

At a glance

~/.origin contains readable artifacts, but the daemon data directory also matters for a complete backup.

After moving or restoring Origin, verify with status, doctor, and a capture/recall round trip from the client you use.

What to back up

Back up the readable artifacts and the daemon application data together. The readable side gives you pages, sessions, status records, and local git history. The daemon data side keeps the database, index, config, and service-facing state.

A backup that only includes ~/.origin may preserve useful Markdown, but it should not be treated as a complete live runtime restore.

Paths

Readable artifacts:
~/.origin/

Daemon application data:
macOS:   ~/Library/Application Support/origin/
Linux:   ~/.local/share/origin/ or $XDG_DATA_HOME/origin/
Windows: %LOCALAPPDATA%\origin\

Keep backups private

Origin memory can contain project decisions, private preferences, client names, sensitive repo details, and old versions preserved by local git history.

Do not put backups in a shared cloud folder, public issue, or team drive unless that is an intentional data-governance decision.

Before moving machines

Install the Origin runtime on the new machine first, then restore the backed-up data into the matching platform locations.

MCP client settings may contain absolute paths to origin-mcp. After migration, rerun origin mcp add for each client instead of assuming old settings still point to the right binary.

Verify after restore

Do not judge a migration from file presence alone. Verify the daemon can read the store, the MCP connector can reach the daemon, and the client can recall a known fact.

If doctor reports path or service problems, fix those before capturing new production memories on the restored machine.

Checks

~/.origin/bin/origin status
~/.origin/bin/origin doctor

# then verify from the client:
/brief
/recall <known project fact>

Plain Markdown fallback

If you cannot restore the daemon immediately, the projected Markdown under ~/.origin is still useful as a human-readable fallback.

That fallback does not provide capture, recall, distill, review, forget, or index updates. Treat it as readable continuity, not a full Origin runtime.

Deletion is separate

Uninstalling Origin's service does not delete memory data. Deleting memory data is a separate decision because it can remove the only local record of project history.

When removing Origin permanently, review what is in ~/.origin and the daemon data directory first. For normal troubleshooting, keep the data and use doctor output to diagnose the install.

Configuration

Know the Origin settings that matter: spaces, MCP client wiring, daemon bind address, local paths, models, and keys.