Gemini CLI Shut Down? Only One Sign-In Method Ended

Saw a post saying Gemini CLI is dead? It is half true at most. The repository is alive. As of August 22, 2026 commits are still landing, the Apache 2.0 license is unchanged, and version 0.56.0 shipped three days ago.

What ended is one sign-in method. Since June 18, 2026 you cannot sign in to Gemini CLI with a personal Google account. And this is the part people miss: it is not just free accounts. Paying Google AI Pro and Ultra subscribers were cut off the same day.

If you landed here you are probably one of two people. Either the install worked but sign-in threw an English error you did not recognize, or you heard something ended and cannot tell whether it applies to you. Both are answered below.

Gemini CLI

A command line tool that lets you use Google's Gemini model from a terminal. Antigravity CLI is the successor Google built for individual users, and it runs with the command agy.

What ended is personal account sign-in, and the repo is still alive

Google announced the transition on May 19, 2026 and it took effect on June 18. That was roughly a month of notice.

Here is the exact boundary.

The paid tiers are where most people guess wrong. It is easy to assume only the free tier got cut, but the official announcement names free users, Google AI Pro, and Ultra together in one sentence. The dividing line is not whether you pay. It is whether the account is personal or organizational.

The repository staying open deserves its own note, because that promise lives in a notice posted in the repository itself rather than in a blog post. Google committed to continued model updates, bug fixes, and security patches for enterprise customers, and to keeping the Apache 2.0 repository open to the community unchanged. That is holding up.

Why this is still confusing: Google's own docs were never updated

This is the most useful part of the article. The transition happened two months ago and people are still getting stuck, and there is a specific reason. Google's own documentation still says the old thing.

The repository README still tells you that a personal Google account gives you 60 requests per minute and 1,000 per day for free. There is not one line about the transition. Anyone arriving fresh reads that sentence first.

The official authentication docs do the same. They instruct individual users to sign in with a Google account, and they specifically tell Google AI Pro and Ultra subscribers to use that subscription account. Both of those paths are now closed.

A pull request to fix this was opened on August 19 and has not been merged as of this writing. Its own description sums the situation up better than anything: the authentication guidance is sending users down a sign-in path that no longer works.

With Google's docs in that state, it is no surprise that third party install guides repeat the same stale instructions. You did not do anything wrong.

Installing today still works, sign-in is where it stops

The install itself succeeds. The npm package is live, so the command runs and the tool lands on your machine. The wall comes right after.

Try to sign in with a personal Google account and you get this.

This client is no longer supported for Gemini Code Assist for individuals.
To continue using Gemini, please migrate to the Antigravity suite of products:
https://antigravity.google

You may also see UNSUPPORTED_CLIENT or IneligibleTierError alongside it. Several users have filed the same symptom in the repository.

If you are seeing this message, nothing is misconfigured. The server rejected the account type. Retrying or reinstalling produces the same result.

Three paths forward: Antigravity CLI, keep your org license, or use an API key

Pick whichever matches your situation.

Individual users move to Antigravity CLI. This is the path Google points to. Accounts without a subscription still receive usage that refreshes weekly. Installation is a single command, and unlike Gemini CLI you do not need to install npm or other developer tooling first. The command to run it is agy.

If you were using a work account, do nothing. An organization's Gemini Code Assist Standard or Enterprise license, or a connection through Google Cloud, continues to work exactly as before.

If you want to keep Gemini CLI itself, the API key path is still open. Authenticate with a key issued from Google AI Studio. The advantage is that you stay on the open source build. One caveat: the announcement says "paid API key" while the documentation just says "API key," so the two sources disagree. Whether a free tier key works is something you will have to test yourself.

Moving to Antigravity CLI: most settings carry over, skills need a manual move

If you had an existing setup, some of it transfers automatically and some does not.

The first time you run agy it offers to find and import your existing configuration. Extensions convert with agy plugin import gemini. Instruction files like GEMINI.md and AGENTS.md are read as they are, so leave them alone.

The manual part is the skills folder. Skills inside a working directory moved from .gemini/skills/ to .agents/skills/. MCP server configuration also used to live inside the settings file and is now a separate file with different key names.

The official migration guide is upfront that the transfer is partial. Skills, rules, and MCP servers are supported, while terminal themes and experimental display settings may not come across.

What you give up: Antigravity CLI is not open source

Before you follow the migration notice without thinking about it, there is one thing worth knowing.

Gemini CLI is Apache 2.0 open source. It has over 100,000 stars and 14,000 forks. Anyone can read the code, change it, and reuse it.

Antigravity CLI is not that. There is a repository, but the CLI's source code is not in it. What you get is documentation, a changelog, demo videos, and a handful of examples. GitHub's language breakdown for the repo is empty. There is no license file, and the executable is downloaded from Google's servers.

An issue asking whether it will be open sourced was filed in May. Google never answered, and it auto closed after 60 days of inactivity.

Why should this matter to someone who never reads source code? Because open source means the community can carry a project forward when the company changes direction. That is exactly the situation we just lived through. Google cut off individual users and Gemini CLI still runs, because it is open. When the same thing happens to a closed tool, there is no fallback.

Gemini CLI transition: what to check right now

Google's documentation is still being updated, so details can shift within days. Check the official docs once more before you install or sign in.