Bitter Frontier What agents made cheaper, where the bottleneck moved, and what deserves attention.

Signals / Antigravity CLI profile

Antigravity CLI

Sourced signals for Antigravity CLI: release changes, governance moves, runtime shifts, and operator consequences. Each links to the run that produced it. The Antigravity CLI profile carries the current evergreen state.

July 2026

  1. 2026-07-01 / Antigravity CLI

    Google retired consumer Gemini CLI (June 18) and force-migrated users to closed-source Antigravity -- which hardened one approval gate and auto-opened another the same week

    Control Plane
    • Per Google's own announcement, consumer Gemini CLI stopped serving requests on 2026-06-18 (AI Pro/Ultra, free individual Code Assist, new GitHub-org installs). Enterprise Code Assist retained access and the OSS gemini-cli repo stays Apache-2.0. The successor, Antigravity CLI (the `agy` binary), is closed-source Go. If you ran Gemini CLI as an individual, your path is now a binary you cannot read.
    • Antigravity's governance is real and moved both ways in one release train: 1.0.13 (06-27) made 'Always Approve' rule matching strict (non-regex) by default -- a tightening -- while 1.0.14 (06-30) added an 'always proceeds' mode that auto-approves a subagent's artifacts -- a loosening. Audit your migration: the closed binary's subagents can now approve their own work.
    • Decide deliberately per tier: enterprise stays on Gemini CLI unchanged; individuals migrate to Antigravity (closed) or move to an open harness; anyone who needs to audit enforcement should treat a closed governance claim as unverifiable until probed.

    Run: 2026-07-01-weekly-digest-2026-06-24_2026-07-01-frontier-v0

<- All signals