Guides
Guides for Claude Code, Cursor and Codex: what a run changed, how to switch agents, and how to review the code before you merge.
- What did Claude Code change?
See which files a Claude Code, Cursor or Codex run changed, read the diff, and get a plain-English explanation of what it means.
- Switch from Claude Code to Codex
Carry a task from Claude Code to Codex: write down the task and the working-tree changes, or use Continue in BuildGist.
- Understand code an agent wrote
Read one agent run at a time, starting from what you asked for, and turn each important change into one plain sentence.
- Hand off Claude Code to Cursor
Hand a task from Claude Code to Cursor: write down the task and the working-tree changes, or choose Continue so the new chat starts with that context.
- Review what Codex changed
Review a Codex run with git status and git diff, read the risky files first, and use the Inbox explanation when the run was meaningful.
- Claude Code hit a usage limit
Claude Code stopped on a usage limit. The files are still in the project folder: read the diff, then continue the task in Cursor or Codex.
- Keep context across agents
Keep a task's context across Claude Code, Cursor and Codex by staying in the same Git folder and choosing Continue when you start a new chat.
- Review AI code before merging
Review AI-generated code before you merge it: read the request, the diff and the risky files, then run the tests that cover what you are about to ship.
- BuildGist or the git diff
Read the git diff for the exact lines, and BuildGist for a plain-English account of one meaningful run. The diff is enough when the change is small and you know the files.
Setup is in Getting started.