What did Claude Code just change?
Last updated: 8 October 2026
At the end of a turn Claude Code tells you what it did. That reply is a summary, written by the model. The files on disk are the record, and the two do not always match: a file the reply never mentions, a key written into a config file, a deletion inside a shell command. Here are the ways to see what really changed.
Read the tool calls
Each tool call shows in the conversation as a line you can expand. A file Claude changes with its file tools appears under the file's name, but a file changed by a shell command appears only inside the command, if at all. In a test on 7 October 2026 with Claude Code 2.1.292, Claude rewrote src/config.js with cat > src/config.js <<'EOF' inside a Bash call, and npm install changed package.json and added package-lock.json; no tool line named those two files:
A shell call is not always drawn as Bash either: in another test that day, Claude Code drew a sed -i call as Update(src\config.js), the way it draws a file edit, and on Windows it ran npm install through its PowerShell tool, PowerShell(npm install is-number) (What /rewind misses). The tool lines say what Claude ran; they are not a list of changed files.
The test project above was not a git repository. In one, Claude Code can list under a Bash call the files that changed while it ran: the bashEditDiffEnabled setting "records which files changed in a Git repository while a Bash command runs", by default in auto mode and bypassPermissions mode. What it leaves out: Review what Claude Code changed before you commit.
Ask git
git status lists, among others, "paths in the working tree that are not tracked by Git (and are not ignored by gitignore[5])" (git status), and git diff HEAD shows the changes to tracked files since your last commit: "Typically you would want comparison with the latest commit, so if you do not give <commit>, it defaults to HEAD." (git diff). It sees what Claude's tools and its shell commands did alike. Its limits: it compares with your last commit, so several turns and your own edits run together; it leaves out files your .gitignore excludes, such as a new key in .env; and it shows nothing in a folder that is not a git repository.
A slip after every turn
turnslip is a Claude Code plugin that snapshots the project's files and compares them at the end of each turn (its README), and prints the difference as one line under Claude's reply, after Stop says:, as in the test above.
- Per turn: only this turn's changes, shell commands included, so
npm installshows up as packages changed. - What went unsaid: Claude ends its reply with a short receipt of the files it changed, which the screen hides unless Claude Code's verbose output is on. A file that changed but is missing from it shows as
not mentioned: config.js; a file it lists that did not change shows assaid but not changed: …. - Risky changes: 🔑 a key written to a file your
.gitignoredoesn't exclude, or a new.env(what to do then), 🗑 deletions, 🗄 migrations, 📦 dependencies, 🚀 pushes and deploys, ⚠ writes outside the project. - Afterwards:
/turnslip:undotakes the turn back. With Pro,/turnslip:historylists the recent turns of the project and/turnslip:reportsums up the session.
Like git, turnslip never reads what your .gitignore excludes, and its free core works with "no account and no network" (README). It works only if it was installed before the turn.
Related: How to undo Claude Code changes · All guides · Install turnslip, free