How do I review what Windsurf changed?
A Windsurf or Cascade run can change files in your workspace, or in a git worktree, before anything is committed. The job is to see what it touched, decide what to keep, and know what is risky, before you merge those edits back or open a pull request. The editor's own review tools, 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 files, including a worktree
In the project folder, git status lists the files that changed and git diff shows the patch. If the session ran in a worktree, review that worktree first, then decide whether to merge it into your main workspace.
Windsurf's Cascade docs, checked November 13, 2026, describe Worktree mode in the Cascade input. You can switch to a worktree only at the start of a Cascade session; a conversation already underway cannot be moved. After Cascade makes file changes in the worktree, click merge to bring them into your main workspace. Worktrees live under ~/.windsurf/worktrees/<repo_name>. git worktree list shows the active ones. Devin Local can also start a session in an existing worktree and bring the changes back with a Merge button.
git status
git diff --stat
git diff
git worktree list
Files you had already edited will appear in that list too. Commit or stash your own work first if you want the list to be only this run.
Checkpoints, then an independent review of the diff
The same Cascade docs describe named checkpoints and reverts. Hover over the original prompt and use the revert arrow, or revert from the table of contents. That restores the codebase to the state at that step. The docs warn that reverts are currently irreversible, so be careful. You can also create a named snapshot of the current project state from the conversation and return to it later.
Quick Review, documented at Devin Desktop's Quick Review page (the same feature Windsurf Enterprise can enable in Devin Desktop settings), checked November 13, 2026, runs a second agent over your local changes. When the agent has edited files, select Quick review. The review agent analyzes the diff and shows feedback in the editor, so you can find issues before you commit. This is a review of the code. It is not a substitute for reading the risky files or running the tests.
If the work is already in a pull request
For Teams and Enterprise on GitHub Cloud, Windsurf's PR Reviews docs, checked November 13, 2026, say you can type /windsurf-review in a pull request comment. Windsurf then posts feedback as GitHub review comments. If Enable Auto Reviews is on, it also reviews a pull request when the pull request is opened as non-draft, or marked ready for review. Automatic reviews are not triggered on drafts; use the comment there.
The same docs also point to Devin Review for pull request reviews. That walk-through is in how to review what Devin changed.
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. Docs last. If the session ran in a worktree, read that diff before you merge it back. 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 Quick Review and your reading of the patch for issues in the lines, BuildGist for the claims check, and 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
Should I merge a worktree before I read the diff?
No. Review the worktree with git diff, and read the risky files, then click merge when you want those changes in your main workspace.
Can I undo a Cascade revert?
The Cascade docs say reverts are currently irreversible. Create a named checkpoint first if you may want that state again, and keep Git as the record you merge.
Does BuildGist review the 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. Quick Review and your own reading of the risky files are the review of the lines.
Sources
- Windsurf: Cascade (checkpoints, reverts and worktrees), checked November 13, 2026.
- Devin Desktop: Quick Review, checked November 13, 2026.
- Windsurf PR Reviews, 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 Gemini CLI changed
- Review what Devin changed
- Review what Cline changed
- Review what Aider 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 Gemini CLI changed
- How to review what Devin changed
- How to review what Cline changed
- How to review what Aider changed
Questions: kayvanandre@gmail.com.