Workflow
How to Share Memory Between Codex and Claude Code
Wenlan keeps one local, source-backed memory store for both tools: Codex connects over MCP, Claude Code through the plugin, and captures from one are recallable from the other.
About this guide
Workflows
Developers using both Codex and Claude Code
5 min read
01
Codex connects through MCP-only setup.
02
Claude Code gets plugin commands and the same daemon.
03
Handoffs make cross-tool continuation explicit.
01
Quick answer
Yes — run one Wenlan daemon as the shared store: connect Codex over MCP and install the Claude Code plugin, then point both at the same data directory and space. A fact captured in Codex can then be recalled in Claude Code, and vice versa. Codex's native Memories and AGENTS.md only help Codex itself; Wenlan keeps memory independent of the tool that wrote it.
Wenlan keeps decisions, lessons, pages, and handoffs independent of the tool that produced them. That lets Codex and Claude Code participate in one work history.
02
When this problem appears
Codex may handle one coding pass while Claude Code handles another. Codex native Memories and AGENTS.md still help Codex itself, but they do not automatically become Claude Code memory.
03
Verify cross-tool memory
Do a small round trip before trusting the workflow.
- Set up Wenlan once.
- Add Codex with ~/.wenlan/bin/wenlan connect codex.
- Install the Claude Code plugin with /plugin marketplace add 7xuanlu/claude-plugins, /plugin install wenlan@7xuanlu, then /setup.
- Capture a harmless project fact in Codex with space X.
- Recall that fact from Claude Code with the same space.
- Reverse the smoke test: capture in Claude Code, then recall from Codex.
Codex and Claude Code smoke test
~/.wenlan/bin/wenlan connect codex
/plugin marketplace add 7xuanlu/claude-plugins
/plugin install wenlan@7xuanlu
/setup
# Use the same Wenlan space for both clients during capture and recall.04
What to check next
Do not use different daemons, data directories, or spaces unless you intentionally want isolated memory stores. MCP-only Claude Code is tools-only; the plugin path is what provides /setup, /brief, and /handoff.
Try the local memory loop
Install Wenlan, connect your AI client, and verify that capture, recall, and handoff work on your machine.
FAQ