Share memory between Codex and Claude Code sessions
A shared memory system lets Codex and Claude Code sessions reference the same rules, artifacts, lessons and decisions, and it syncs.
Source
@taayjuss on X · 2026-10-16
Written in our own words. Credit to the original author. Link checked 2026-10-24.
What they did
A shared memory system lets Codex and Claude Code sessions reference the same rules, artifacts, lessons and decisions, and it syncs.
Result (as claimed)
Switching agents does not mean starting from zero.
Tools they used
Cost: Pricing depends on the tools you pick; check each official pricing page.
Set it up
Pick a contained repo or task
Start on a branch or side project where mistakes are cheap.
Install and configure
Set up Codex, Claude Code. Read what it can run on your machine and limit permissions where possible.
Run it on a real task
Give it a well-scoped issue and let it work. Review the diff like any pull request.
Add guardrails
Keep tests and CI in the loop, and never let an agent push to main or touch production secrets unattended.
Copy the full setup prompt
Paste into your agent and it will walk you through the setup, asking before anything that sends, posts or spends.
You are helping me set up this AI use case end to end in Claude Code. Goal: Share memory between Codex and Claude Code sessions What the original author did: A shared memory system lets Codex and Claude Code sessions reference the same rules, artifacts, lessons and decisions, and it syncs. Reported result (as claimed by the author): Switching agents does not mean starting from zero. Source: https://x.com/taayjuss/status/2110898405019189575 Tools they used: Codex, Claude Code Category: Dev & ops Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
You are helping me set up this AI use case end to end in Codex. Goal: Share memory between Codex and Claude Code sessions What the original author did: A shared memory system lets Codex and Claude Code sessions reference the same rules, artifacts, lessons and decisions, and it syncs. Reported result (as claimed by the author): Switching agents does not mean starting from zero. Source: https://x.com/taayjuss/status/2110898405019189575 Tools they used: Codex, Claude Code Category: Dev & ops Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
You are helping me set up this AI use case end to end in Grok Bot. Goal: Share memory between Codex and Claude Code sessions What the original author did: A shared memory system lets Codex and Claude Code sessions reference the same rules, artifacts, lessons and decisions, and it syncs. Reported result (as claimed by the author): Switching agents does not mean starting from zero. Source: https://x.com/taayjuss/status/2110898405019189575 Tools they used: Codex, Claude Code Category: Dev & ops Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
The Daily 5
Get five new use cases tomorrow morning
Free. Real sources. Unsubscribe any time.
Guides for this use case
How to save, share and resume coding agent sessions · How to vibe code classroom apps and quizzes as a teacher · How to use Claude Code and Codex together · How to learn anything with an AI tutor
Related use cases
Have CLAUDE.md import AGENTS.md so Claude and Codex share rules
Dainer_Jun's CLAUDE.md just imports AGENTS.md and routes the work, Codex reads AGENTS.md on its own, and work state lives in files too.
Have Claude Code review your Codex build from your phone
From his phone, ZazenCodes gets Codex on his computer to spin up Claude Code and pull its review of what Codex built.
Run Claude Code and Codex agents together from one local dashboard
ahmedaghadi built acom, a local dashboard to launch Claude Code and Codex agents across projects, follow their activity, pass messages and handle interruptions.
Keep Claude Code and Codex on one rules file with a symlink
rthiago found CLAUDE.md said pnpm while AGENTS.md said npm, so the two agents kept rewriting the lockfile. He keeps one file and symlinks the other: ln -s AGENTS.md CLAUDE.md.