What did Claude Code change?

Kayvan Zahiri · October 10, 2026

In the project folder, git status lists the files that changed and git diff shows the changes. That works for Claude Code, Cursor and Codex, whether or not anyone has committed. BuildGist writes a plain-English explanation, and flags concerns, after each meaningful run.

List the files

git status
git diff --stat

git status includes files you had already changed before the run. Commit or stash your own edits first if you want the list to be only the agent's. Files the agent created show up as untracked until they are added.

Read the changes

git diff
git diff HEAD

git diff is what is not staged yet. git diff HEAD is everything since the last commit, staged or not. If the agent made commits during the run, read those too:

git log --oneline -5
git show

git show takes the commit id from that log.

Read the risky files first

Start where a small change has large consequences: sign-in, sessions and permissions; anything that deletes or overwrites data; payments; new dependencies; configuration. A one-line change to an auth check can deserve more of your attention than a long rewrite of a readme.

An example: Add login with Google

This is the example on the BuildGist home page. The caption there says it is from a real Claude Code run, shortened and edited.

The request was "Add login with Google."
7 files changed, +224 -16.
In plain words: the sign-in button, where Google sends you back, the browser's signed-in status, and deleting a note.
What it means: Google checks who visitors are and vouches for them, so the app never sees passwords. The name for that is the OpenID Connect (OIDC) authorization code flow.
Concern, high: any signed-in user can delete anyone else's note. Nothing checks that the note is yours.

Sign-in worked. The delete path asks for sign-in and does not check who owns the note.

The same read, from BuildGist

BuildGist explains each meaningful Claude Code, Cursor and Codex run in plain English, flags concerns, and carries the task over when you switch agents. Explanations show up in your Inbox, including from uncommitted work. No commit or push is needed. Small changes stay quiet. Each explanation says what changed, what it means and what to check. It is written by AI, so check important behavior against the code and tests.

An explanation can include edits you made by hand between agent turns.

After a run

git status, for which files changed.
git diff --stat, for how much changed in each.
Read auth, data deletion, payments, dependencies and configuration first.
For each of those, ask what a user can now do that they could not before.

What you need

A Mac with Apple silicon and macOS 12 or later.
Claude Code, Cursor or Codex.
A Git project. No commit, push, remote or GitHub repository is needed.
A GitHub account, to sign in. BuildGist does not access your GitHub repositories.

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.

Questions: kayvanandre@gmail.com.