Getting started
What you need
- A Mac with Apple silicon and macOS 12 or later.
- Claude Code, Cursor or Codex.
- A Git project, with no commit, push, remote or GitHub repository needed. A plain folder is not recorded; when your agent works in one, BuildGist for Mac offers to make it a project with a click.
- A GitHub account, to sign in. BuildGist does not access your GitHub repositories.
Set up
- Download BuildGist. Choose Download for Mac, open the download and double-click BuildGist. It copies itself to Applications.
- Sign in and connect your Mac. Choose Sign in to BuildGist and sign in with GitHub in the page that opens. When your browser asks, choose Open BuildGist (Safari says Allow). Nothing is sent before this.
- BuildGist gets your coding agents ready. It sets up each supported agent it finds and says You're ready. Codex needs you to approve BuildGist once, in Codex; BuildGist shows the steps.
- Code normally.
- Your explanations appear in your Inbox automatically, from uncommitted work too. Small changes stay quiet.
- Switch agents without losing the thread. 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; Start fresh skips it. Nothing is handed over unless you choose Continue.
Stop or remove
In BuildGist for Mac, choose Disconnect this Mac to stop syncing, or Uninstall… to remove BuildGist. Neither touches your projects. To delete your account and its synced data, go to Settings → Delete my account.
Known limitations
- An explanation can include edits you made by hand between agent turns.
- To explain a run, BuildGist sends its changes to the AI provider it uses, and secret masking is best-effort. Privacy has the details.
- BuildGist runs only on Macs with Apple silicon for now.
Help
Open BuildGist on your Mac to see whether each coding agent is set up. Still stuck? Email kayvanandre@gmail.com.
Guides
Guides lists each of these with a one-line summary.
- What did Claude Code change?
- Switch from Claude Code to Codex
- Understand code an agent wrote
- Hand off Claude Code to Cursor
- Review what Codex changed
- You’ve hit your session limit in Claude Code
- You’ve hit your usage limit in Codex
- Keep context across agents
- Review AI code before merging
- BuildGist or the git diff
- Claude Code session history
- Undo Claude Code changes
- BuildGist vs CLAUDE.md, AGENTS.md and HANDOFF.md
- Keep context from Claude Code to Cursor
- Resume an agent session in another tool
- BuildGist vs Conductor
- Codex context window full
- Undo Codex changes
- Cursor usage limit reached
- Review Cursor agent changes
- Codex session history location
- Your conversation is too long in Cursor
- One default coding agent, or two?
- Tools that summarize agent sessions
- Switch from Codex to Claude Code
- Move from Cursor to Claude Code
- Switch from GitHub Copilot to Claude Code
- Move from Windsurf to Cursor
- Switch from Gemini CLI to Claude Code
- Coding agent crashed mid-task
- Claude Code lost context after compacting
- What commands did the agent run?
- Turn an agent session into a PR description
- Which coding agents read AGENTS.md?
- Switch from Cursor to Codex
- Export a Claude Code conversation
- Keep the dead ends when you switch agents
- Write a handoff note for a fresh session
- Usage limit hit in the middle of a task
- Mac apps that explain agent runs
- Explain a Claude Code session
- What did my agent change before I merge?
- BuildGist vs an AI PR reviewer
- Review what Claude Code changed
- Review what Copilot changed
- Review what Windsurf changed
- Review what Gemini CLI changed
- Review what Devin changed
- Review what Cline changed
- Review what Aider changed