BuildGist

How do I review what Cline changed?

Kayvan Zahiri ·

Cline records a checkpoint after each file edit or command, so you can see what changed at every step and roll the files back without throwing away the conversation. That is the review path when Cline has been moving quickly, including with auto-approve. Compare on a checkpoint, then a 30-second claims check on BuildGist, gets you to the risky files first.

Check a PR or paste a session

A ready-made example opens on the same page if you just want to look.

Compare the checkpoint, not only the last message

Cline's checkpoint docs, checked November 13, 2026, say that every time Cline modifies a file or runs a command, it saves a snapshot of your project files. After each tool use, a checkpoint indicator appears in the conversation, with Compare and Restore. Click Compare to open a diff of exactly what changed at that checkpoint, in your editor's diff viewer, across all the affected files. If Cline edited three files in sequence, you get three checkpoints, and you can inspect or restore each one on its own.

Cline keeps those snapshots in a shadow Git repository, separate from your project's Git history. Your own repository stays untouched. Checkpoints also capture files Git is not tracking, and they persist across editor sessions. Checkpoints are on by default. You can turn them off in Cline settings, under Feature Settings, if you need to.

Restore when the code went the wrong way

Click Restore next to any step for three choices:

The same docs describe a typical auto-approve workflow: let Cline work through the task, review the result, and if something is wrong, restore to the last good checkpoint and give more specific guidance. When you edit a previous message and choose Restore All, Cline restores the files to the checkpoint at that point before it resubmits the edited message.

None of those restores is a Git commit or a Git reset. When you are ready to keep the work, review it in your own repository:

git status
git diff --stat
git diff

git status includes files you had already changed. Commit or stash your own edits first if you want the list to be only this run. Files Cline created show up as untracked until they are added. The docs recommend using Compare to inspect changes before you commit them to Git.

Read in order of risk

Start where a small change has large consequences: sign-in, sessions and permissions; anything that deletes, overwrites or sends data; payments; new dependencies; configuration, including CI and new external services. Docs last. Compare is especially useful after a long auto-approve stretch, because it shows each step's diff, not only the final tree. For each important change, finish the sentence "Now a user can ...". If you cannot, keep reading that file.

What BuildGist adds

BuildGist answers a narrower question: did the agent do what it said, and what did it touch that it did not tell you about?

Paste a public GitHub pull request or a git diff at /try. The check compares the claims with the files in the diff and leads with three lists: files or tests the claims name that are not in the diff, changed files the claims never mention (risky ones first), and test claims with no test file or test run behind them. That comparison is plain matching. No AI writes it. Under it, BuildGist adds a plain-English explanation, written by AI, of what changed and what to check, and a short handoff you can copy into a fresh session.

BuildGist does not comment on bugs in the changed lines, suggest fixes, run your tests or prove the code is correct. The explanation can be wrong. The diff is still the thing you merge. Use Compare to inspect each checkpoint, BuildGist for the claims check on what you plan to commit, and your own reading of the risky files plus the tests before you merge.

The by-hand claims check is in how do I know what my coding agent actually changed before I merge? When the diff alone is enough is in BuildGist or the git diff. A fuller merge checklist is in how to review AI-generated code before you merge.

Questions

Do Cline checkpoints change my Git history?

No. They are stored in a shadow repository. Your Git history stays under your control. Commit only after you have compared the checkpoints you want to keep.

If I restore files, do I lose the conversation?

No. Restore Files reverts the code and keeps the conversation, so Cline still has the context and can try a different implementation.

Does BuildGist review Cline's lines for bugs?

No. It checks what the run said it did against the files that changed, explains the change in plain English, and writes a handoff. Compare, and your reading of the risky files, are the review of the lines.

Sources

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 Download for Mac

No Mac handy? Try it in your browser: paste a session or a git diff and see the explanation.

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

Related

Using another agent?

Questions: kayvanandre@gmail.com.