From Claude Code to Codex, without losing the thread.
By the Olomni team · Updated
With Olo, when a task ends the AI notes where it was left; the next AI you open in that project (say Codex after Claude Code) receives that note on start, along with the branch, changed files and whether tests passed. It all lives on your computer, with keys and tokens redacted.
Step by step
- Connect Claude Code and Codex to Olo.
- Work with Claude Code. When it finishes, it notes where the task stands.
- Open Codex in the same project folder, or choose Continue with… in Olo.
- Codex receives the handoff as context on start and picks the work up.
What the handoff includes
What the AI noted (decisions, dead ends, next step) and what Olo observes by itself: git branch, names of uncommitted files and whether the last test, build or lint passed. Observed data is labelled as such, to tell it apart from what the AI claims.
What keeps it safe
Notes that look like instructions, links or secrets are held for your review instead of passing to the next AI. Keys and tokens are redacted and the handoff never leaves your computer.
How the AIs use it
Olo offers a local MCP server (olomni-local) with three tools: handoff_get to read where the project was left, handoff_note to leave a decision, dead end or next step, and handoff_thread for the working thread.
Frequently asked questions
Does it work between any pair of AIs?
Between Claude Code, Codex, Cursor and Gemini CLI, and any agent that speaks MCP.
Are my notes uploaded to the cloud?
No. The handoff is stored only on your computer.
Do I have to copy and paste the context?
No. With “Continue with…” Olo prepares the handoff and opens the other AI in the project folder.