I had another pull request open and asked Codex something like this.
Is an agent already working on the other PR? If so, can you ask it to bump the version?
I’d been trying to stick with ChatGPT to keep things manageable. I expected Codex to find another chat in its sidebar.
Turns out Claude Code had opened the PR. Codex found the idle Claude session and picked it back up. Claude pushed the bump to the same PR, and Codex checked it on GitHub.
1. Resume a saved Claude conversation
Codex used the PR branch to find Claude’s worktree and ran this from there.
claude --print \
--resume "<claude-session-id>" \
"Bump the version."
Claude continued the saved conversation in a separate process. The worktree gave it the right files, and --print returned the reply in the shell. The request went only to that process.
Claude Code can use the same trick to resume a Codex chat.
codex exec resume \
"<codex-chat-id>" \
"What's left on this PR?"
I checked the reverse syntax with codex exec resume --help. So far I’ve only handed work from Codex to Claude.
Two ways to reach a live Claude session
For the PR bump, --resume was the simplest option because I just needed the result back in Codex. To see a message arrive in the Desktop chat I already had open, I could use a relay. If I could set up the receiving session ahead of time, a channel would let me send directly.
2. Relay through Sonnet
Codex started a temporary Claude CLI process with --print --no-session-persistence --model sonnet. It gave Sonnet just two tools. ListAgents found the open Desktop session, and SendMessage delivered the message to its inbox. Claude Code cross-session messaging
Codex verified receipt in the Desktop session’s transcript. The relay took an extra model turn to send the message, and the receiving session still handles its own action approvals.
3. Send directly through MCP Channels
I asked Codex to try MCP Channels in a dedicated, interactive Claude Code terminal session. Codex enabled the custom channel when it started that session. Channels are still in research preview. Anthropic’s Channels reference
Codex sent a Python HTTP POST to a temporary one-way Node MCP server on localhost, using a bearer token. The server declared claude/channel and forwarded the message over stdio as notifications/claude/channel.
Codex found the incoming <channel> event and Claude’s exact reply, CODEX-CHANNEL-678293, in the same transcript. The only Claude model turn was the receiver’s reply. Codex stopped the listener and removed the temporary files.
Maybe paying for both ChatGPT and Claude wouldn’t be so bad after all.