Reviewing Changes
See what the agent touched, then stage and commit — without leaving the chat.
In the chat itself
Every chat's composer shows a running summary of changes: file count and a
+N −M line count, right where you're already typing. Click it to open a
diff for any changed file, inline or side-by-side.
In the Agent Hub
Each chat row in the Agent Hub shows a second line summarizing the latest
turn — something like Edited App.css −3 +41, or −12 +34 · 3 files when
more than one file changed. You can tell what an agent just did without
opening its tab.
Committing
The composer's Changes pill has a commit split-button with a few paths:
commit, commit and push, or create a branch first. Staging happens
automatically for anything that isn't conflicted — pick a message (prefilled
from your last prompt if there is one) and go. When an agent runs git commit itself via a shell command, a small pill appears above the composer
with the short hash, message, and push state, so you always know if a
change made it into history without checking the terminal.
In the editor
Any tracked file gets a Changes button in its tab toolbar — a diff against HEAD, inline or split, independent of which chat touched it.