Profiles / Google
Antigravity CLI
Google retired the coding CLI you could read, and shipped one you have to trust.
Operator Stance / as of 2026-07-01
- Use it for
- Individual and consumer users who relied on Gemini CLI and need a Google-supported terminal agent now that the open one stopped serving them, and teams already in the Antigravity ecosystem who want terminal reach plus background multi-agent orchestration.
- Avoid it for
- Any operator who must audit the enforcement behind an approval or sandbox claim -- the code is closed, so a governance guarantee rests on the changelog, not readable source. If you need an open, self-hostable CLI, the gemini-cli OSS repo (Apache-2.0) or another open harness is the honest choice.
- Watch next
- Whether subagent 'always proceeds' auto-approval hardens into a default gap; whether Google publishes verifiable enforcement docs for the closed binary; and the real behavior-change cost of migrating off Gemini CLI.
Antigravity CLI -- the agy binary -- is Google's closed-source, Go-written
successor to consumer Gemini CLI. It joins the watchlist this cycle because it is
now the path Google points individual users to: on
2026-06-18 Gemini CLI stopped serving requests
for AI Pro/Ultra, free individual Code Assist, and new GitHub-org installs.
Enterprise Code Assist retained access, and the open-source gemini-cli repository
remains Apache-2.0 and enterprise-serving -- so the retirement is tiered, not total,
and Antigravity is the consumer tier's replacement (see the gemini-cli
profile for the other side).
What makes it a watchlist entry and not just a rename is the trade it asks an
operator to accept. Gemini CLI was open source: an approval rule or a sandbox
boundary was, in principle, readable. Antigravity is closed. Its governance model
is real and active -- and this window it moved in both directions in one release
train. 1.0.13
(2026-06-27) hardened command permissions, making "Always Approve" rule matching
strict and non-regex by default (regex is now opt-in behind a regex: prefix),
which closes a class of over-broad approve rules. Three days later,
1.0.14
(2026-06-30) loosened it, adding an "always proceeds" mode that auto-approves a
subagent's artifacts -- delegated work proceeding without the confirmation the
parent flow may require. The sandbox model (a proceed-in-sandbox mode that
auto-approves commands inside the secure sandbox, with .git on the dangerous-path
list) is genuine, but you verify it by reading the changelog, not the code.
That is the lens to hold Antigravity through: it is both the market-succession story (a tier-1 vendor retiring an auditable CLI and force-migrating consumers to a closed one) and the closed-source-governance story (a control you must trust rather than inspect). The profile will deepen as the changelog and any local probes accumulate; the current claims are seeded from its late-June release train.
Verification
closed source releases / evidence floor: official changelog / updated 2026-07-01
Verified claims
- 2026-07-01-antigravity-successor-to-gemini-consumer / verified 2026-07-01
- 2026-07-01-antigravity-in-window-release-train / verified 2026-07-01
- 2026-07-01-antigravity-strict-approve-matching / verified 2026-07-01
- 2026-07-01-antigravity-subagent-auto-approve / verified 2026-07-01
- 2026-07-01-antigravity-sandbox-model / verified 2026-07-01
Open Questions
Featured in
- Foreground Attention Is No Longer the Control / 2026-07-02
- Patched for Whom / 2026-07-01
Source policy: what Frontier watches and accepts as evidence
Edited and maintained by Bitter Frontier.