Google Antigravity release notes: CLI 1.0.11–1.0.12 tighten projects and permissions

Google Antigravity shipped two close CLI releases on June 24: 1.0.11 and 1.0.12. This is not a new Antigravity 2.0 desktop release. It matters more for teams that use the terminal as a real workspace for coding agents: project selection, authentication, permission precedence and review controls all become easier to reason about.

Google Antigravity is Google's agent platform for development work. Antigravity CLI is the terminal-first surface where a coding agent can read projects, suggest changes and continue longer workflows without putting everything inside an IDE. An approval gate is the point where a human must approve the next step before the agent can run commands, write files or use more sensitive access.

Source: Antigravity CLI 1.0.12 on GitHub, Antigravity CLI 1.0.11 on GitHub and Antigravity CLI CHANGELOG.md.

Google Antigravity release notes: what changed in CLI 1.0.11 and 1.0.12?

1.0.12 adds the --project and --new-project launch flags, so users can set or create projects more explicitly at startup. The same release also changes permission config merging: project-specific settings in ~/.gemini/config/projects/ should take precedence over global CLI settings in ~/.gemini/antigravity-cli/settings.json.

That matters in everyday work. If a Swedish consultant, developer, or automation lead runs several customer projects from the same machine, a global default rule should not accidentally override the project's own limits. This release makes the project boundary easier to read.

1.0.11 is more about the working session itself. ctrl+c becomes a clearer stop key: the first press cancels active agent work, while a double press starts the exit flow. /resume should load faster with a metadata cache and parallel loader. Tool confirmations can open in a larger AltScreen view with ctrl+g, and USE_ADC=1 agy is verified in the changelog as the Application Default Credentials mode, meaning Google's local default sign-in method for Cloud environments.

Source: 1.0.12 release notes describe --project, --new-project and permission precedence. 1.0.11 release notes describe ctrl+c, /resume, ctrl+g and USE_ADC=1 agy.

Why this matters for governed agent workflows

This is a control release more than a wow release. But control releases often decide whether AI agents can be used in real workflows.

For Hammer readers, the practical question is simple: can the team see which project the agent is working in, which permission file applies, how it authenticates to Google Cloud and where a human should stop or approve the next step? With 1.0.11 and 1.0.12, more of those hooks are visible in the CLI.

Try it first in an internal repository before connecting heavier systems. Put API keys in environment variables or a secret manager, use scoped permissions per project, redact sensitive output in run logs and make write actions depend on manual approval. That is not bureaucracy. It is the difference between a helpful coding agent and a black box with terminal access.

Source: Antigravity CLI changelog lists permission precedence, ADC mode, stop keys and tool confirmations. The public Google Antigravity changelog still shows 2.1.4 from June 11 as the latest desktop app note, so this article covers the CLI track.

Short example: use the new Antigravity feature

Human step first: start Antigravity CLI in the right codebase. If the team uses Google Cloud sign-in, USE_ADC=1 agy is the source-verified ADC mode. If you need to select a project explicitly, check local help for the exact argument format and use the new --project or --new-project flags documented in release 1.0.12.

Then paste this prompt into the agent once the CLI session is already running in the right project:

You are already running in the intended Google Antigravity CLI project.
Map this repository's agent-control setup after the 1.0.11 and 1.0.12 CLI updates.
Check project-specific permissions first, then global CLI settings.
Identify one task where a scoped approval gate is needed, one place where ADC/project selection should be documented, and one review step that benefits from the new diff or tool-confirmation controls.
Return a short run note with files inspected, settings paths, and what a human must approve before writes.

Good output should show:

• Which project-specific permission file or settings surface applies,
• whether any global CLI setting could be misread,
• where USE_ADC=1 agy, --project or --new-project belongs in the team's runbook,
• which manual approval is needed before the agent writes, runs commands or changes permissions.

What to watch next

Watch two things. First, whether Google moves more Antigravity CLI documentation from GitHub into the public Antigravity site. Second, whether the project flags and permission precedence are followed by more detailed policy or admin controls. That is where Tool Forge work becomes concrete: not more loose prompts, but small agent routines with a project boundary, authentication, review mode and a log.