BuildGist FAQ
BuildGist is a Mac app for people who code with Claude Code, Cursor or Codex. After each meaningful run, it explains in plain English what the agent changed and what to check. When you switch agents, it hands the task to the new chat, so you don't explain it again.
Every question here was asked by a real person: in a reply to us on X, in an email, or in a public post on X or Hacker News. The wording is lightly edited.
Does BuildGist write the summary on its own when a session ends, or do I trigger it?
On its own. After each meaningful Claude Code, Cursor or Codex run, the explanation appears in your Inbox, from uncommitted work too. There is nothing to click, and no commit or push is needed. Small changes stay quiet, so not every run gets one.
When I switch agents, does the new one get the whole history or just a summary?
Neither, exactly. When you start a new chat in another coding agent in the same project, a BuildGist card offers the earlier agent's task. Choose Continue and the new chat starts with that task's context: what you asked for, and constraints you typed while the task was underway. When the last run's files are still as that run left them and HEAD has not moved, it can also say how many files that run changed, whether a test failed, and up to three paths.
The transcript stays in the agent you left, and the patch is not included. The code is already in the folder, where the new agent can read it.
What happens when both agents touched the same files?
Both agents work in the same project folder, so the second one sees the first one's edits on disk. BuildGist does not lock, merge or reorder anyone's edits. It explains each run on its own, so you can see which run changed what. To keep two agents that run at the same time out of each other's files, give each task its own Git worktree. BuildGist vs Conductor covers that.
When you switch agents, do you paste the error message or the whole diff?
With BuildGist, neither: the changes are already in the folder, and Continue gives the new chat the task. Without it, paste a short note: what you asked for, word for word, what is done, the error or failing test, and the files that changed. Let the new agent read the diff itself with git diff rather than pasting it. Keep context across agents has the steps.
How do I move my Codex context into a new Claude Code session?
Claude Code cannot read the Codex chat, so move the task, not the transcript. With BuildGist on your Mac, start a new Claude Code session in the same project and choose Continue on the BuildGist card. Claude Code takes the context on a new session, not a chat you are in the middle of. Without BuildGist, ask Codex for a short note (the request, what is done, the next step) and paste it as your first message. Resume an agent session in another tool has both ways.
How do I keep working when I hit my coding agent's usage limit?
Switch to another agent in the same project and carry the task over. With BuildGist, start a new chat in Claude Code, Cursor or Codex and choose Continue on the card. By default the card offers a task whose last activity in this project was within 12 hours, so for a limit you hit yesterday, write a note instead. In Cursor, the handoff is best effort: if the new chat does not show the task, paste the note. The guides quote each limit message: Claude Code, Codex and Cursor.
An agent fixed a bug in seconds and I don't know what it changed. Deploy, review every change, or roll back?
Review before you deploy. Start with git status and git diff to see every file it touched. A BuildGist explanation is a quick first read of what changed, what it means and what to check, but it is written by AI, so check important behavior against the code and tests. If you cannot say what the change does, do not ship it yet. Review AI code before merging has the checklist.
Is there a cap on how many runs a month BuildGist Pro explains, or is it unlimited?
No monthly cap. Each account has a daily limit on what its explanations cost. Past it, new explanations wait until the next day begins (00:00 UTC), and your coding agents keep working as usual. Pricing has the plan.
Still have a question?
Email kayvanandre@gmail.com. Pricing answers the cost, privacy and Mac questions, and Getting started has the setup.