Google Antigravity release notes: CLI 1.1.0 makes diff review the default

Google Antigravity release notes often look like terminal housekeeping. This one is more useful than that: Antigravity CLI 1.1.0 makes review before file writes the default behavior. For teams letting a coding agent touch real projects, that changes the workflow.

Google Antigravity is Google's agentic IDE, a development environment where an agent can read, reason about and change code inside a workspace. A coding agent is an AI assistant that can plan and perform development tasks in a repository. An approval gate is the human checkpoint before a change is saved.

Google Antigravity release notes: what changes in CLI 1.1.0

Google published Antigravity CLI 1.1.0 on July 8, 2026. The main change is request-review, which the release notes describe as the default mode: the CLI automatically pauses before file write operations and shows an interactive line-level diff. In that diff view, the user can review, accept or reject individual code modifications before they are saved to disk. The release notes also mention the f shortcut for the diff preview.

Source: Google Antigravity CLI 1.1.0 release notes

That makes Antigravity more useful in real workflows. The agent can still do the work, but the stop point moves to the right place: just before the file changes.

The modes are easier to control

The release notes say execution modes can now be cycled publicly in the order default -> accept-edits -> plan. They also describe a new Agent Mode option in /settings, where the user can set and persist a default mode such as default, accept-edits or plan without editing settings.json or starting the CLI with --mode.

Google also says /plan replaces the older /planning, and that /fast has been removed. That matters if your internal playbooks, onboarding notes or checklists still mention the old commands.

Source: Google Antigravity CLI 1.1.0 release notes

Why it matters for practical teams

For a Nordic team testing AI in code, integrations or internal tools, this is a good version to build a routine around. You can let the agent do more than suggest text in a chat tab while still requiring human review where it counts.

Three things are worth testing today:

• Whether request-review shows the change before it is saved.
• Whether new files get the separate Create file preview, which the release notes describe for write_to_file without overwrite.
• Whether /settings saves the right Agent Mode for your normal workflow.

Keep the control layer practical. Use workspace-scoped repo access, environment variables or a secret manager for keys, redact sensitive output and save decisions in a simple run log. That is enough to make agent work usable without slowing it down.

Short example: use the new Antigravity feature

Human step: update or open Antigravity CLI 1.1.0, choose the Agent Mode you want in /settings or cycle mode with shift+tab. Use /plan when you want the agent to plan first. Those commands and UI steps come from the release notes; do not put them inside the agent prompt.

Then paste this prompt into the agent once the right mode is selected:

Review the next change in this repository using Antigravity CLI 1.1.0 request-review behavior.
Start by naming the files you expect to touch and why.
Make the smallest useful edit set, then stop at the diff preview so I can approve, reject, or comment before anything is saved.
Return a short receipt: files changed, reason for each change, and what I should test after approval.

Good output should show:

• Which files the agent expects to touch and why.
• A diff that can be read before the change is saved.
• A clear point where the human approves, rejects or comments.
• A short test suggestion after approval.

For Hammer readers, this fits Tool Forge work especially well: build a routine where the agent can help for real, but diff review, approval and the run log are part of normal delivery.

What we did not see in this round

The public Google Antigravity app changelog was still on 2.2.1 from June 25 when this article was written. The google-antigravity SDK package was still on 0.1.5 on PyPI. The new, clear signal in this coverage window was CLI 1.1.0.

Source: Google Antigravity Changelog

Source: google-antigravity on PyPI