How do I review what Aider changed?
Aider is built around Git. Each time it edits a file, it commits the change with a descriptive message, so you can review the work as a series of commits, undo the last one, or inspect the uncommitted patch since your last prompt. That is faster than rereading the chat. Aider's own commands, plus a 30-second claims check on BuildGist, get you to the risky files first.
A ready-made example opens on the same page if you just want to look.
See the last turn, then the commits
Aider's Git integration docs, checked November 13, 2026, say /diff shows all the file changes since the last message you sent. That is the patch for the turn you just ran, even when earlier turns are already committed. The in-chat commands reference, checked the same day, lists /diff the same way: display the diff of changes since the last message.
Whenever Aider edits a file, it commits those changes with a descriptive commit message. That makes the run easy to review in Git history, and easy to undo. Inspect the recent commits with:
git log --oneline -10
git show
You can also run raw Git commands from the chat with /git. The output is excluded from the chat, so it is a way to look at history without adding it to the conversation.
Keep your edits separate, and undo a bad turn
Aider takes special care before it edits files that already have uncommitted changes. It first commits those preexisting changes with a descriptive message, so your work stays separate from Aider's, and so you do not lose your work if a later edit is wrong.
/undo undoes and discards the last change. Use it when the latest commit is not what you wanted. Git remains the record of everything before that. /commit commits dirty changes that were made outside the chat, with a sensible message (you can pass one). /lint lints and fixes files in the chat, or all dirty files if none are in the chat.
The same docs describe flags that turn parts of this off: --no-auto-commits stops Aider from committing each of its changes, --no-dirty-commits stops it from committing dirty files before it edits, and --no-git stops it from using Git at all. The docs do not recommend those for normal use. If auto-commits are off, review with git status and git diff the way you would for any uncommitted work, and commit yourself when you are ready.
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. Because each Aider edit is its own commit, you can walk the risky files commit by commit with git show, instead of one large uncommitted patch. 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 /diff and git show to read Aider's commits, BuildGist for the claims check, 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
Does /diff show the whole session?
No. It shows file changes since the last message you sent. For earlier turns, use git log and git show, because those turns are already committed.
Will Aider mix my uncommitted work with its edits?
Not by default. If a file is already dirty, Aider commits your preexisting changes first, then makes its own edit in a separate commit.
Does BuildGist review Aider'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. /diff, git show, and your reading of the risky files are the review of the lines.
Sources
- Aider: Git integration (
/diff,/undo, auto-commits), checked November 13, 2026. - Aider: In-chat commands, checked November 13, 2026.
- Git: git diff, checked November 13, 2026.
- BuildGist's try page and privacy page.
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 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
- 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
Using another agent?
- How to review what Claude Code changed
- How to review Cursor agent changes
- How to review what Codex changed
- How to review what Copilot changed
- How to review what Windsurf changed
- How to review what Gemini CLI changed
- How to review what Devin changed
- How to review what Cline changed
Questions: kayvanandre@gmail.com.