BuildGist

How to switch from Claude Code to Codex

Kayvan Zahiri ·

Before you leave Claude Code, write down the task and what already changed in the working tree. Open Codex in the same folder and give it both. You can do that by hand, or let BuildGist carry the task over.

What does not come with you

Opened in the same folder, Codex can read those uncommitted files. It was not in the earlier chat, so the reason they changed is not in front of it unless you put it there.

By hand

See the files

git status
git diff --stat
git diff

You do not need to commit. The commands only show you what is in the working tree.

Write a short note

Use your own task. This one follows the Google sign-in example on the BuildGist home page, so the "not done" line is that example's high concern, not a second feature of the product.

Task: Add login with Google.
Done so far: the sign-in button, where Google sends you back, and the browser's signed-in status. See the diff.
Not done: deleting a note does not check that the note belongs to the signed-in user.
Next step: add that check.

Paste it as the first message. Ask Codex to say the task and the next step back before it edits anything.

The note goes stale

You have to remember to write it when you switch. The next time you switch, the note still describes the older task. It is written for the next agent, so you still read the diff yourself to see what changed.

Continue in BuildGist

BuildGist works with Claude Code, Cursor and Codex. When you start a new chat in another coding agent in the same project, a BuildGist card at the bottom right of your screen offers the earlier agent's task. Choose Continue and the new chat starts with that task's context. Choose Start fresh to skip it. Nothing is handed over unless you choose Continue.

BuildGist also writes a plain-English explanation after each meaningful run, so you can read what the first agent changed before you hand the task on.

What you need

Codex needs you to approve BuildGist once, in Codex. BuildGist shows the steps. Setup is in Getting started.

To explain a run, your computer sends BuildGist what that run needs, and BuildGist passes it to Anthropic. BuildGist does not keep this material. It does not send your whole repository, files the run did not change, or files named like secrets, such as .env files and keys. It keeps the explanation and short cited excerpts of changed code, at most 12 lines each. Secret masking is best-effort. Privacy has the full list.

Every account gets 7 days of BuildGist Pro free, with no card. The 7 days start at your first explanation or Continue handoff. Nobody is charged when the trial ends. After that, BuildGist Pro is $12 per month, plus any applicable tax shown at checkout. See pricing.

Try BuildGist

Apple silicon, macOS 12 or later. United States, 18 or older.

Related

Questions: kayvanandre@gmail.com.