Setup
How to Add Memory to Claude Code
Install Wenlan's Claude Code plugin, run /init, and verify a local memory round trip.
Article packet
Workflows
Claude Code users who want persistent project context
5 min read
01
Install the Wenlan 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/claude-plugins, then /plugin install wenlan@7xuanlu, then /init. Restart Claude Code once if prompted before running /init.
Wenlan 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/claude-plugins.
- Run /plugin install wenlan@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/claude-plugins
/plugin install wenlan@7xuanlu
/init
/capture Wenlan test: this project uses Wenlan for local AI work memory.
/recall Wenlan local AI work memory04
What to check next
Do not start by capturing full logs or command output. Wenlan works best when each memory is one durable idea with why it matters.
Try the local memory loop
Install Wenlan, connect your AI client, and verify that capture, recall, and handoff work on your machine.
FAQ