What changed on June 18, 2026?

Google announced the move on the Google Developers Blog on May 19, 2026, in “An important update: transitioning Gemini CLI to Antigravity CLI”. The post says that on June 18, 2026, Gemini CLI and the Gemini Code Assist IDE extensions stop serving requests for Google AI Pro and Ultra, and for individuals using Gemini Code Assist for individuals at no cost. Code Assist on GitHub stopped taking new installations on GitHub organizations. Gemini CLI's own quota page, last updated June 18, 2026, puts it shortly: “Unpaid tier and Google One users: Gemini CLI was replaced by Antigravity CLI on June 18th, 2026.”

Gemini CLI is still maintained for the remaining paid routes. Its quota page notes that it “has not been optimized for Gemini 4 Argon” and sends Argon users to Antigravity. So even a paid API-key user who wants Google's newest model ends up in agy.

How do I install and sign in to Antigravity CLI?

# macOS, Linux, Googlebook$ curl -fsSL https://antigravity.google/cli/install.sh | bash# Windows PowerShellPS> irm https://antigravity.google/cli/install.ps1 | iex# check the install, then start it$ agy --version$ agy

The binary goes to ~/.local/bin/agy on macOS and Linux, and to C:\Users\<username>\AppData\Local\agy\bin on Windows. On first launch you pick a color scheme and a rendering mode (Alt-Screen or Inline). You also confirm that you trust the repository directory before agy indexes any files.

Three ways to sign in

• Google account (default). Run agy and your browser opens. Over SSH, agy prints a URL instead: open it on your local machine and paste the code back. Tokens are kept in your operating system's keyring, and /logout removes them.
• Gemini API key. Set modelProvider to gemini in ~/.gemini/antigravity-cli/settings.json and export GEMINI_API_KEY. Google warns that setting the variable on its own does nothing. agy does not read GOOGLE_API_KEY or .env files.
• Google Cloud (ADC). Run gcloud auth application-default login --project <id> and set AGY_ADC_AUTH=true. You can also set GOOGLE_CLOUD_QUOTA_PROJECT and GOOGLE_CLOUD_LOCATION.

What carries over from Gemini CLI?

The first time you run agy, it finds your old Gemini CLI profile and offers to move your session into the OS keyring. Most project setup keeps working, with a few manual steps:

Which commands replace /stats?

The habit that breaks most often is checking usage. Gemini CLI's /stats mixes session token counts with quota. Antigravity CLI splits quota and credits into separate panels and does not show a running token count for the session.

How quotas and refreshes differ

The unit changes as well as the command. Gemini CLI counts requests per user per day, for example 1,500 on Code Assist Standard and 2,000 on Enterprise. Antigravity groups models (Gemini Flash and Pro in one group, Claude and GPT in another), and each group has a five-hour limit and a weekly limit. Google publishes how often each plan refreshes, but not how large the limits are:

AI Credit Overages has two settings. With Never, agy waits for the refresh. With Always, it spends credits once baseline quota is gone and goes back to baseline when it refreshes. In the CLI, the useG1Credits setting, or Use AI Credits under /config, does the same thing.

Where each tool keeps its logs

Both tools sit under ~/.gemini/, but they do not share a log. After the move, a month of Google agent work can be split across two places: Gemini CLI session files from before June 18 and Antigravity conversation databases from after it.GEMINI_CLI_HOME moves Gemini CLI's folder, so check it if your old sessions seem to be missing.

How whoburnedmore counts each tool

whoburnedmore treats the two as separate tools, so your history keeps going across the move instead of stopping on June 18. Gemini CLI is read from its local session logs. Antigravity is counted as local token totals from CLI 0.9.25: whoburnedmore counts tokens from Antigravity's local conversation databases, but not remaining quota, older encrypted-only history, or Agent API usage.

If Antigravity is installed, the status check explains what it reads. These lines are printed by the whoburnedmore CLI command npx whoburnedmore status (abridged to the Antigravity part):

$ npx whoburnedmore status  • Google Antigravity detected. Its usage is read from the local    conversation databases (~/.gemini/antigravity*/conversations/*.db).    Older Antigravity versions kept only encrypted logs with no token    counts; that history can't be counted. Update Antigravity if none shows.

1. 1

   Confirm you were moved

   If you signed in with a personal Google account on free Code Assist, Pro or Ultra, Gemini CLI stopped serving you on June 18, 2026. Seat and paid-key users can stay.
2. 2

   Install agy and import your setup

   Run the installer, start agy, accept the session migration, then run agy plugin import gemini and move workspace skills to .agents/skills/.
3. 3

   Relearn the usage commands

   /usage for quota, /credits for credits, and /context for the context window.
4. 4

   Keep one history across both

   Update to whoburnedmore CLI 0.9.25 or later so Antigravity's local token totals appear next to your old Gemini CLI sessions. More on limits in Google Antigravity usage limits and on the old tool in how to check Gemini CLI usage.

Sources checked November 8, 2026: Google Developers Blog, May 19, 2026, Gemini CLI quota and pricing, Antigravity CLI quickstart, Antigravity CLI authentication, Migrating from Gemini CLI, Antigravity CLI commands, /usage, CLI AI credits, Antigravity plans, gemini-cli repository docs, and the whoburnedmore CLI source.