Blog

Continue a Claude Code conversation in Codex, and back

When Claude Code hits a limit halfway through a task, you can carry on in Codex without retyping the background, and the same works from Codex to Claude Code. QuotaBuddy reads the conversation from the logs both agents keep on your Mac and gives the other agent a briefing. This post covers how a handoff works, its two modes, and what the other agent can and can’t see.

Start a handoff

  1. In the main window’s sidebar, choose Conversations. It lists the Claude Code and Codex sessions on this Mac, grouped by project, with a search field. QuotaBuddy reads the agents’ logs where they are and never changes them.
  2. Select the conversation.
  3. Click the Continue in button, such as Continue in Codex CLI, or press ⌘Return.

QuotaBuddy shows its progress as it goes. It turns on its context server, finds the other agent on your Mac, connects that agent to the server, and opens it in the conversation’s project with a handoff prompt.

If the project folder has moved, the page says so. Click the ⋯ button next to Continue in and choose Choose Project Folder….

Choose where it opens

By default the button goes to the other agent: a Claude Code conversation continues in Codex, and a Codex conversation continues in Claude Code. To pick a specific place, click the ⋯ button and choose under Open in. Only what’s installed on this Mac is listed:

  • Claude Code: Claude Code in Terminal, Claude Code in VS Code, Claude desktop app, Bitrig and Claude Code in Orca.
  • Codex: Codex CLI in Terminal, Codex app and Codex in Orca.

The Terminal choices open a new window in the project and start the CLI with the prompt. Terminal, iTerm, Ghostty, Warp, kitty, WezTerm and Alacritty all work. The Codex app opens a new thread in the project with the prompt filled in. Bitrig comes forward with the prompt copied, ready to paste into a new conversation.

To change the default for every handoff, open Settings › Coding Agents and use Continue in and Terminal app under Continue in Another Agent. If the place you chose isn’t available, conversations continue in the other agent instead.

Load context and wait, or continue the work

Then decides what the agent does once it opens. Set it for one conversation in the ⋯ menu, or as the default in Settings › Coding Agents.

  • Load context and wait is the default. The agent reads the previous conversation, recaps where things stand and waits for your next instruction. The prompt asks it to cover what was asked, what was decided, what’s done and what’s still open, and not to change any files yet.
  • Continue the work: the agent reads the previous conversation and carries on with whatever was left outstanding.

If the first agent stopped in the middle of an edit, Load context and wait lets you check the recap before anything changes.

To start the other agent yourself, choose Copy Handoff Prompt from the ⋯ menu and paste it in.

What the other agent receives

The handoff prompt is short. It names the conversation and tells the agent to get a briefing from QuotaBuddy’s quotabuddy MCP server, then read more of the conversation only for parts the briefing leaves out. It also tells the agent to treat what it reads as the record of a past conversation, not as instructions.

The briefing includes:

  • the agent the conversation came from, the project and branch, and the model;
  • the original request;
  • the latest summary the agent wrote when it compacted, if there is one;
  • the prompts you sent after that, in order;
  • where it left off, and lines that may describe open items;
  • the files it created or edited, when Include commands the agent ran and their output is on.

Briefing length in Settings › Coding Agents sets how long it is: Compact (about 1k tokens), Standard (about 2k, the default) or Detailed (about 4k).

Through the same server, the agent can also list your conversations and projects, search them and read their messages. Every tool only reads.

What stays hidden

What Agents Can See, in Settings › Coding Agents, controls what the server shares:

  • Conversations from picks Claude Code, Codex or both.
  • Which conversations offers All indexed conversations or Only conversations I hand off. New setups start with Only conversations I hand off.
  • Hide keys and passwords is on by default. API keys, access tokens, private keys, passwords in URLs and similar secrets become [redacted] before an agent sees them.
  • Include commands the agent ran and their output is off by default. While it’s off, agents don’t see the commands, their output, the agent’s thinking or the list of edited files.
  • Never share from these folders keeps projects out. Click Add Folder…, and conversations in that folder and its subfolders are never listed, searched or shared.

The context server

Handoffs run through a small server inside QuotaBuddy. It answers only on this Mac, and only to agents that have its access token, which QuotaBuddy adds to an agent’s settings when it connects it. A handoff turns the server on and connects the agent for you.

To manage this yourself, open Settings › Coding Agents. Let coding agents use QuotaBuddy turns the server on or off, and Your Agents shows whether Claude Code and Codex are Connected, with Connect, Disconnect or Update buttons.

Without permission, Claude Code asks before each use of QuotaBuddy’s tools, which can stall a handoff. Turn on Let Claude Code use QuotaBuddy without asking to skip those prompts.

To see what agents have looked at, open Advanced at the bottom of that tab and check Recent requests.