Google is retiring Gemini CLI on July 17. The terminal-agent wave, and owning your CLI

On May 19, 2026 at Google I/O, Google said it is consolidating its developer tooling under one brand, Antigravity, and retiring the standalone Gemini CLI and the Gemini Code Assist IDE extensions in the process. A tool that a lot of developers used as a free, model-in-your-terminal agent is being folded into a cloud platform.

Here are the verified dates, what actually changes, and an honest read on what it means if your terminal agent belongs to someone else.

What is happening

• Announced at I/O on May 19, 2026. Google is unifying its agent tooling into Google Antigravity and sunsetting the standalone Gemini CLI plus the Gemini Code Assist IDE extensions.
• June 18, 2026 is the cutoff for individuals. Gemini CLI and the IDE extensions stopped serving requests for the free Gemini Code Assist tier and for Google AI Pro and Ultra users on that date.
• Gemini Code Assist for GitHub is going too. No new installs on GitHub organizations after June 18, and requests stop being served in the weeks after, with the tool fully wound down by July 17.
• Enterprise is exempt, for now. Organizations on a Gemini Code Assist Standard or Enterprise license, or using it through Google Cloud, keep their access.

What you get instead: Antigravity CLI

Antigravity CLI is available to everyone now. It is the terminal surface of Google Antigravity, Google's agent-first development platform, alongside a server-side harness. Google kept the features people leaned on most: Agent Skills, Hooks, Subagents, and Extensions (now called plugins). In Google's own words, there is no “1:1 feature parity right out of the gate.”

The catch is the shape of it. Antigravity CLI runs against Google's cloud and Gemini models only, and usage is gated behind the Google AI Pro and Ultra tiers. If the thing you liked about Gemini CLI was pointing a terminal agent at whatever model you wanted, running it cheaply, or running it without a subscription, that is not what this is. It is a funnel into one vendor's cloud and one family of models.

The bigger picture: terminal agents won 2026

Gemini CLI is not disappearing because terminal agents failed. The opposite. 2026 is the year the terminal became the default surface for AI coding. Claude Code normalized it, and a lot of developers who used to avoid the terminal now run an agent in it every day.

• opencode is the most-starred coding agent on GitHub, north of 180,000 stars and MIT-licensed, ahead of Claude Code (around 135,000), Gemini CLI (around 106,000), and OpenAI Codex (around 94,000).
• Around 35 actively maintained CLI coding agents existed as of early July 2026. This is a crowded, fast-moving category, not a niche.
• The benchmarks live here too. On the Terminal-Bench leaderboard in early July, Codex CLI paired with GPT-5.5 led at roughly 83%, with Claude Code on Opus 4.8 close behind near 79%.

The reason is simple. The terminal sits next to git, tests, build scripts, and deploy commands, which is where real engineering automation happens. A terminal agent is scriptable, easy to drop into CI, model-agnostic if the tool allows it, and able to run locally. For a lot of developers it is the most stable place to work, precisely because it does not depend on a specific editor or a vendor's cloud.

The catch: a CLI you don't own can be switched off

The Gemini CLI shutdown is not a strange event. It is the pattern. Two weeks ago we wrote about Cursor acqui-hiring Continue.dev, another bring-your-own-model tool that got folded into a paid product, with its hosted data deleted after July 15. Same month, different tool, same ending.

When your terminal agent is a venture-funded product or a vendor's on-ramp to a paid cloud, its lifespan is a business decision, not a technical one. The features can be great and the model can be the best available, and it can still be retired on a Tuesday because the strategy changed. You usually find out from a deprecation notice with a date on it, the way Gemini CLI users just did.

What owning your CLI looks like

The two things that survive a shutdown are the ones you control: open-source code you can fork and pin, and a local setup that runs on your own machine with your own keys. That is the entire argument for local-first, bring-your-own-model tools. If the agent runs where you run it, and the model is yours, a vendor's roadmap change is a headline, not a migration.

That is the bias behind Bodega One Code's CLI, which we shipped as v0.1.0. It is a terminal client for the same local-first agent as the desktop app: QEL-verified edits, air-gap mode, and bring-your-own-LLM, driven from your shell as an interactive TUI or fully headless for scripts and CI. It shares one brain with the desktop app, so your providers, MCP servers, and sessions carry over. There is no cloud requirement and no subscription. You can install it with a one-liner:

curl -fsSL https://github.com/BodegaoneAI/bodegaone-cli-releases/releases/latest/download/install.sh | sh

Honest caveats, since this post is about not getting rug-pulled: it is v0.1.0 and the whole product is in open beta, so expect rough edges, and it is not open source. If open source is your hard line, opencode and Aider are the right calls, and both are excellent. If not depending on someone else's cloud is the point, that is what we are building. Windows, macOS, and Linux installs and the full command reference are on the CLI docs.

What to do next

1. If you use Gemini CLI on a free, Pro, or Ultra plan, move before July 17. Enterprise access via a Standard or Enterprise license or Google Cloud continues for now, but the individual path is closing.
2. Decide what you actually want from a terminal agent. A vendor's cloud model with the newest features (Antigravity CLI, Codex, Claude Code), an open-source harness you maintain (opencode, Aider), or a local-first agent you own (Bodega One Code). For a deeper look at Google's side, see our Antigravity comparison.
3. Keep your provider config and keys portable. Store your model list and API keys somewhere the next tool can read, so switching is a config change and not a rebuild.

Sources

• Google Developers Blog - “Transitioning Gemini CLI to Antigravity CLI”
• The Register - “Bye-bye, Gemini CLI; Google nudges devs toward Antigravity” (May 20, 2026)
• github.com/google-gemini/gemini-cli discussion #27274 - retirement dates and migration
• opencode on GitHub - star count and license
• Morph - CLI coding agent leaderboard and agent count (2026)