Skip to content

Setup

How to Add Memory to Claude Code

Install Origin's Claude Code plugin, run /init, and verify a local memory round trip.

Qi-Xuan LuUpdated 5 min read

Article packet

01

Workflows

02

Claude Code users who want persistent project context

03

5 min read

01

Install the Origin Claude Code plugin from the marketplace.

02

Run /init once to verify the daemon, MCP wiring, and first memory round trip.

03

Use /brief, /capture, /recall, and /handoff as the daily loop.

01

Quick answer

Use the Claude Code plugin path: /plugin marketplace add 7xuanlu/origin, then /plugin install origin@7xuanlu, then /init. Restart Claude Code once if prompted before running /init.

Origin adds that durable layer without turning Claude Code into a new app. The plugin gives slash commands; the daemon keeps local memory; MCP lets other clients share the same context.

02

When this problem appears

Claude Code can do substantial work in one session, but the next session starts cold unless the decisions, gotchas, and project state are stored somewhere durable.

03

Install and verify

Run the plugin setup first, then prove the loop with one harmless capture.

  • Run /plugin marketplace add 7xuanlu/origin.
  • Run /plugin install origin@7xuanlu.
  • Restart Claude Code if it asks, then run /init and wait for the daemon, MCP, and local memory checks to pass.
  • Run /capture with one durable project fact, then /recall with a specific query.
  • End a real work session with /handoff.

Claude Code commands

/plugin marketplace add 7xuanlu/origin
/plugin install origin@7xuanlu
/init
/capture Origin test: this project uses Origin for local AI work memory.
/recall Origin local AI work memory

04

What to check next

Do not start by capturing full logs or command output. Origin works best when each memory is one durable idea with why it matters.

Try the local memory loop

Install Origin, connect your AI client, and verify that capture, recall, and handoff work on your machine.

FAQ

Do I need an API key to add memory to Claude Code?+
No for the core local memory loop. Optional model or API-key paths add richer background distillation, but setup and daily capture/recall do not start there.
Is MCP-only setup enough for Claude Code?+
It can be enough for raw tools, but the plugin is the richer path because it adds slash commands like /brief, /handoff, /distill, and /init.