Seamless Claude and Codex handoff.
Start in Claude, continue in Codex, then switch back on the next prompt. Composer carries the context so you do not have to re-explain the work in another terminal.
Ask Composer to build, debug, or review
Workflows
The handoffs people already do by hand.
Composer turns the copy-paste relay between Claude and Codex terminals into one continuous agent thread.
Plan: extract token refresh into a guarded helper.
Reviewed — flagged a missing token-expiry case.
Plan, then review
Have one agent sketch the approach and the other challenge it before code changes start.
Plan: extract token refresh into a guarded helper.
Reviewed — flagged a missing token-expiry case.
Plan, then execute
Hand a plan from Claude to Codex, or from Codex to Claude, and let the next agent run with it.
Plan ready: 3 steps across auth + tests.
Start both, pick one
Send the same first prompt to Claude and Codex, compare the first pass, then continue from the thread you trust.
What's this project about?
Composer is a multi-provider coding agent — a desktop app, a CLI, and a shared local runtime.
A monorepo: an Electron desktop app, a React/Ink CLI, and a Next.js landing page.
Switch the next turn
Send the next prompt to whichever agent fits the moment, then switch back without starting a new terminal conversation.
Shipped the migration and ran it locally.
Next: add a rollback test for the down path.
FAQ
What is Composer?
Composer is a meta-harness that orchestrates harnesses like Codex, Claude, and others into one unified harness across shared context, sessions, and agents.
What does shared context mean?
Composer keeps the active codebase, session history, tool results, diffs, and review notes together so Codex and Claude can work from the same picture.
Why compose Codex and Claude?
Different agents are useful as independent passes on the same work. Use one to plan, another to implement, and either one to challenge the result without rebuilding context from pasted summaries.
How does handoff work?
Handoffs happen through shared sessions and thread context instead of copy-pasting summaries between separate chats. The next agent can pick up the task with the relevant state already nearby.
What carries across threads?
Composer keeps track of the workspace, previous turns, changed files, review comments, and agent outputs so follow-up work can stay grounded in the actual project.
What workflows does this unlock?
Planning with Claude and reviewing with Codex, implementing with Codex and asking Claude to critique the design, or running parallel approaches while keeping the diffs, notes, and tool output comparable.