The useful post-transition story is not that Gemini CLI simply handed everything to Antigravity. By June 23, the public trail shows two live surfaces: Antigravity release and support pressure on one side, Gemini CLI code and PR repair work on the other.
The public trail
Antigravity CLI release 1.0.10 is still the latest visible release in the June 23 recheck. Its changelog points at operator concerns: log-path exposure, auth handling, shell behavior, permission matching, and settings preservation.
The human pressure is visible in issue #415. Users continued reporting authentication breakage after 1.0.9, and a maintainer-side June 22 follow-up asked for reproduction context across version 1.0.8, Antigravity 2.0 or IDE behavior, account plan, network/VPN/proxy conditions, and debug network-diagnostics.
The split
Gemini CLI does not look frozen in the same window. PR #28000 remains an open draft around format-aware write_file repair for JSON, notebooks, YAML, TOML, dotfiles, and infrastructure files.
Gemini CLI PR #28063 also merged on June 21 as commit be7ba2c22, fixing workspace publish failures and changing scheduler yielding after a reported macOS parallel-tool hang.
Why operators should care
For agent operators, this changes the watch model. Antigravity is where packaging, auth/network troubleshooting, permissions, terminal behavior, and migration support are visible. Gemini CLI remains where open implementation details, release machinery, and tool-safety repairs can still be inspected in code.
That distinction matters because the public evidence levels are different. Antigravity exposes release notes, docs, binaries, and issue traffic. Gemini CLI exposes implementation diffs and PR review. A serious migration read has to use both without pretending they prove the same thing.
The conversation to open
The next factual question for Google maintainers is whether the Antigravity support surface will publish enough diagnostic detail for operators to distinguish account eligibility, network policy, proxy behavior, and CLI regressions without depending on issue-thread triage.
The next question for Gemini CLI watchers is whether PR #28000 lands as a repair to structured file editing. If it does, the transition story becomes less like replacement and more like a split between packaged operator experience and still-visible open engineering.