2026-06-18: The Day gemini Went Away
As of June 18, 2026, Google stopped serving free, AI Pro, Ultra, and individual requests through the Gemini CLI and the Code Assist IDE extension, migrating them to the Antigravity 2.0 CLI. Organizational Standard and Enterprise contracts kept running, but any automation leaning on an individual tier halted that day. The new Antigravity CLI was rewritten in Go and shares its harness with the desktop app, yet it shipped without full feature parity with the Gemini CLI it replaced.
What Broke Was a Shell Line, Not an API
The damage was wide because the break landed on a command name, gemini, rather than an API key. Any CI/CD job or deploy shell script that invoked that command directly failed on June 18 with no grace period. A single vendor product-integration decision simultaneously disabled every call site scattered across the codebase.
The Blast Radius an Adapter Layer Absorbs
An adapter layer is a thin abstraction that hides agent CLI invocation behind one module. The pipeline calls only an internal interface such as run_agent(prompt, files), and that interface translates into whatever the real command is — gemini, antigravity, or a rival vendor's CLI. When a vendor changes a command name, argument format, or auth scheme, the edit is confined to a single adapter file while the rest of the pipeline stays untouched.
Designing the Adapter and the Routine That Keeps Vendors at Arm's Length
(a) Planning and target numbers: the first metric is the count of direct CLI call sites across the repo, with a target of 0. Establish a baseline with grep -r "gemini ", then drive that count down each sprint until every invocation sits behind the adapter. The second metric is vendor-switch time — whether swapping to a new CLI stays within one adapter edit plus a smoke re-run and converges under half a day.
(b) Failure patterns: the incident exposed three archetypes. First, hardcoding the vendor CLI throughout the pipeline, so dozens of jobs turned red at once on cutoff day. Second, being force-migrated to the Antigravity CLI without verifying feature parity, where the command runs but old flags no longer apply and outputs drift silently. Third, having no fallback CLI on hand, so automation stopped entirely and recovery fell back to manual work.
(b') Recovery branches: with an adapter, recovery is one command-string swap. Keep a primary and secondary CLI inside the adapter, and when the primary fails on exit code or smoke check, fall back to the secondary path automatically — so a vendor cutoff is absorbed as a route change rather than a pipeline stop. Jobs that hit the fallback should log the CLI and version used, so you can later tally which vendor carried how much load.
(c) Operations checklist: keep alternate CLIs, rival vendors included, under continuous smoke testing. Run a short prompt against the real command at least once daily to measure the fallback-path smoke pass rate, and alert the moment it drops below 100% — ahead of a real outage. Fold vendor-announcement monitoring into a weekly operations routine, pinning a calendar step where a human reads developer blogs and release notes every week. Dated shutdowns like June 18 are pre-announced, so the weekly check is the only cushion against a grace-period-free cutoff.
The adapter opens more than defense. That same June, OpenAI's Codex added a Bedrock provider, widening the choice of execution backends; when call sites converge on an adapter, you can add such a new path behind the interface, measure its cost and latency, and adopt it deliberately. Instead of one vendor's shutdown stopping the pipeline, another vendor's expansion enters as an option.
(d) Improvement loop: each week, review the fallback smoke pass rate alongside the number of newly introduced direct calls. If a new script starts calling a vendor command around the adapter, the control point leaks again, so add a CI lint rule that detects direct gemini and antigravity invocations and hold the count at 0. If switch time is not shrinking release over release, the adapter has hardened into just another bypass point rather than an abstraction.
Vendor Switches That End in a One-Line Change
The lesson of 2026-06-18 is not to pick vendors better; it is to stop a vendor decision from cutting through your pipeline. Converge direct CLI call sites to 0, hold the alternate-path smoke pass rate at 100% across vendors, and put vendor announcements in a weekly routine — and the next forced migration is contained to one adapter file and a single command string.
References
An important update: Transitioning Gemini CLI to Antigravity CLI — Google Developers Blog
Gemini CLI will stop working from June 18, 2026 — Hacker News