Inspect an agent’s changed files

Inspect the actual edits behind an agent’s result before deciding what to keep.

Before you start

Use the completed conversation for the task you want to review. Changes shown in the project Git panel can include other work, so distinguish the agent’s Files changed card from the whole repository.

The diff shows the requested navigation label added to index.html. The separate Git panel also exposes unrelated project changes, which must not be assumed to belong to this task.

Step by step

1. Read the final response and note what the agent says it changed, what it checked, and any unfinished work.

2. Find Files changed in the conversation. Check the filenames and addition/deletion counts against the requested scope.

3. Choose Open diff to inspect the changes together, or open a particular file from the card.

4. Read the removed and added lines with their surrounding context. In the demo, the only implementation edit adds aria-label="Main navigation" to the existing nav element.

5. Use Open File when you need more surrounding code. Check behavior in Preview or your usual runtime as well; a plausible diff is not a functional test.

6. If the result is wrong, return to the conversation with a focused correction. Describe the expected behavior and the relevant file rather than asking for an unspecified rewrite.

What to expect

You can explain what changed and whether it matches the intended task before committing or shipping it.

Troubleshooting and useful details

The demo Git panel also contains an unrelated untracked notes file. Its presence does not mean this agent created it. Review file provenance and selection before delivery. An empty Files changed card can be valid for read-only work; a completed response alone is not proof of an implementation.