Git
Review the Agent's work as commits and diffs, switch branches, and roll back safely — a visual audit trail of every code change.
When an Agent writes code, you want a clear record of what changed and the ability to roll it back. The Git tab gives you a visual view of the version history in the Agent's Drive — a complete audit trail of every file the Agent has touched.
What the Git tab shows
- Commit history — a chronological list of commits in the repository
- Changed files — the files modified in each commit, with
+/-counts - Diff view — inline before/after for any file
- Branch selector — switch branches when the Agent works across several
How the Agent uses Git
As it completes coding work, the Agent can commit automatically. Each commit carries a descriptive message, the exact files changed, and a timestamp — so you can review the Agent's work before merging it anywhere.
Reviewing a commit
Click any commit to expand it, then click a changed file to open the diff:
- const timeout = 5000;
+ const timeout = 10000; // increased for slow networksRed lines were removed, green added, grey is unchanged context.
Rolling back
Click Revert next to a commit to undo its changes. Revert creates a new commit — it never rewrites history.
Revert is non-destructive. Your full history is always preserved.
Give the Agent real repo access
By default the repo the Git tab shows lives only in the Agent's sandbox. To let the Agent push to and pull from an actual GitHub repository, connect a GitHub App installation for this Agent — from the chat composer's + menu → Integration → OAuth → GitHub, or from the Agent's Integrations settings. Only an editor of the Agent can connect or disconnect it; once connected, everyone chatting with the Agent shares the same access, and the Agent's sandbox picks up a GitHub token automatically — no manual environment variables needed. See GitHub app for the details and how this differs from the Developer Portal's per-user connection.
Advanced operations
The Git tab is a visual, read-focused interface. For merges, rebases, remotes, and the like, switch to the Terminal and use the git CLI — changes there reflect in the Git tab automatically:
git log --oneline -20
git checkout -b feature/new-experiment
git remote add origin https://github.com/your-org/your-repo.git
git push -u origin mainFor other providers, or if you'd rather manage credentials yourself, store them or an SSH key via environment variables.