Git panel and terminal land inside Antigravity 2.0
Promtime
googleGoogle has put Git version control and an embedded terminal into the right-side panel of Antigravity 2.0, where repository review now splits into three views: Agent Edits, Uncommitted and Branch. The update was detailed by Testingcatalog, which describes a sidebar wired directly to the Git working tree.
At a glance
- The panel tracks the Git working tree itself, so it registers edits made by an agent, a separate editor, a Python program or a Bash script, and diffs the branch against origin/main.
- Developers can open modified files, search inside diffs, switch between split and unified layouts, stage or unstage files, draft or preview a generated commit message, and commit without leaving the sidebar.
- Before the update, checking what an agent had actually changed often meant leaving Antigravity to run git status or git diff; the adjacent Terminal tab now handles those commands in place.
Agent-driven editing has outgrown the review surfaces built for it: a panel that only lists what the agent's own editing tool touched leaves side effects from scripts, build steps and human edits invisible. Reading the working tree instead appears to be the cheaper fix, and it moves Antigravity closer to the review loop developers already trust. The addition of a terminal in the same workspace reads as an attempt to keep verification inside the app rather than in a second window.
The Git panel registers edits from Bash scripts and other editors
The revised sidebar connects to the Git working tree directly, so it registers file changes regardless of which tool produced them. Work written by a separate editor, a Python program or a Bash script appears next to agent edits, and the Branch view compares the current branch against origin/main.
That addresses a gap in the earlier interface, where developers frequently had to step outside Antigravity and run git status or git diff before they could rely on what the review pane displayed. Antigravity 2.0 previously surfaced agent edits in the same sidebar, without the wider picture of the branch and the working directory.
A staged-changes view handles staging, commit messages and commits
Modified files can be opened from the panel, diffs searched, and the layout switched between split and unified views. A staged-changes view covers selecting files, staging and unstaging them, drafting a commit message and committing from the sidebar, without a separate Git client or an editor window.
Antigravity can also generate a commit message automatically and show it for preview before the commit is created. The adjacent Terminal tab, sitting next to the version-control views, covers the rest of the workflow: tests, linters, builds, package commands and other utilities, with Google's demonstration showing git status and go test ./... executed in place.
The Antigravity Team frames the update around reviewability and trust
The Antigravity Team presents the release as a step toward reviewability and trust in AI-assisted development, with the Git-backed view reflecting the state of the branch and the working directory instead of a single tool's edit history. The terminal and the version-control pane together let teams inspect agent output and verify side effects from other tools.
In an August 25 post on X, Anshul Ramachandran described native Git workflow management and a native terminal for one-off Bash commands as a common request, and tied the timing to the capability level reached by models such as Gemini 3.7 Flash, framing the update as removing the switch to a separate terminal.
What the simulation lets users try
An interactive simulation accompanies the release and covers view switching, diff inspection, terminal commands and the commit flow, though Google notes its appearance may differ slightly from the shipping product. No rollout timing for the panel has been given, and there is no detail on which Antigravity tiers or platforms receive it first.
Comments
No comments yet. Be the first.
Join the conversation
Sign in with Google to leave a comment. Your name and avatar come from your Google profile, and the comment appears after moderation.
We only use your name and avatar from Google. We never store your email address.
