Why VS Code Review View Changed for AI Edits

Why is Visual Studio Code review view showing AI-generated edits differently now

Visual Studio Code now reviews AI-generated edits through the Chat view and the Agents window, not just the older single-file style people expected. The workflow changed because agent edits can touch multiple files, use checkpoints, and open as multi-file diffs or focused single-file diffs depending on the session and settings.

The part people get wrong is assuming “review view” is one fixed screen. VS Code now has two main agent surfaces, the Chat view and the Agents window, and they share the same sessions and settings while still presenting review differently. That is why the same AI change can look like a list of changed files in one place and a diff editor in another.

For agent-generated changes, VS Code now emphasizes file-level review first. In the Agents window, selecting a file in Changes opens a diff view, and by default that can be a multi-file diff editor covering the session’s edits. If you want a tighter read, VS Code provides a setting to open a focused single-file diff instead.

The inconvenient part is that the old mental model, “the AI made a change, now I accept or reject it in one place,” no longer matches how the product works. The agent can apply and save edits directly in the session folder or isolated worktree, so review now looks more like source control review than a temporary suggestion bubble.

That shift also explains why the UI feels more like Git review than inline autocomplete. VS Code documents the same core actions you use for human changes, including diff navigation, side-by-side or inline diff layout, Source Control review, and pull request-style follow-up. The product is steering AI edits into the same verification path as real workspace changes.

Another reason the view looks different is that VS Code now distinguishes between agent edits and pending edits made through the older extension-host workflow. When the agent host is not enabled, the extension host uses a different review flow, and VS Code marks those edits as pending with indicators in the Explorer and editor tabs. That can make the same AI work appear under a different review pattern depending on how the session ran.

This is also why comments and feedback feel more granular now. In the modern review flow, you can select a range inside a changed file, add feedback, and send it back to the agent. Markdown files follow the same pattern through Locked mode, which means the review experience is no longer only about approving a whole file. It is about steering specific lines inside the file.

If you opened VS Code months ago and now see more compact or more visual diffs, that is not random. Recent Copilot release notes say you can review changes faster, see per-file addition and deletion counts, use a more compact diff view, and switch between inline and side-by-side diffs. In other words, the review screen itself has been tuned to show more context in less space.

The other part people miss is that review behavior can change with session state. VS Code now supports checkpoints, file-change summaries, and restoring state across reloads. If you move from the Chat view to the Agents window, or reopen a session later, the editor can restore the session’s side-pane width, active editor, and per-file collapsed state, so the same edits can look visually different without the underlying code changing.

If you want the old shape of review back, the practical move is to look at the diff layout controls and the session settings rather than hunting for a missing feature. In the docs, VS Code points to Show Side by Side Diff, Show Inline Diff, and the openSingleFileDiff setting for getting a narrower review surface. That is the supported path, not a workaround.

A concrete example helps. Say Copilot changes three files in one session: a React component, a test file, and a config file. In the Agents window you may first see the file list, then a multi-file diff for the whole session. In Chat view you may instead inspect the changed file from the agent response, then step through pending edits one file at a time. Same change set, different review lens.

What happens when you ignore the new layout is usually confusion, not data loss. You may think VS Code is hiding edits, when it is really grouping them into a session view, a checkpoint view, or a source-control-style diff. The safe habit is to review the changed-file summary, open the file diff, and then run tests before you commit or integrate anything.

The short version is simple: VS Code changed the review experience because AI edits are now treated as multi-file, session-based work instead of isolated one-off suggestions. The surface changed, the diff layout changed, and the navigation changed, but the core idea did not. You still verify the code before you trust it.

If you want to keep this workflow straight, use the surface that matches the job. Chat view fits code-first iteration next to your editor, the Agents window fits a broader session and file-change review, and Source Control fits final validation before commit. DevConnect’s own workflow guidance is built around the same idea, work on your own code, review changes explicitly, and keep the verification step visible. https://devconnectplatform.com

FAQ

Is this a bug or an intentional change It is an intentional product change. Microsoft’s current docs describe separate Chat view and Agents window review flows, plus multi-file diffs, checkpoints, and session-based change review.

How do I get back to a single-file diff view Open the diff toolbar and switch the layout, or enable the setting that opens a focused single-file diff. VS Code documents both the inline and side-by-side diff options for AI edits.

Why do some AI edits appear as pending changes while others do not That depends on whether the agent host is enabled and whether the edit came through the older extension-host workflow. The docs say older sessions or non-agent-host edits use a different pending-edit path.

Can I still review AI changes before committing them Yes. VS Code documents review in the diff editor, Source Control, and pull request workflows, and it explicitly recommends validating changes before you commit or integrate them.

Where do I give feedback back to the agent In the Agents window diff view, select a range of code and use Add Feedback. In GitHub Copilot code review, you can also apply or discard suggested changes directly from the review comment.