Gemini CLI Says "Client No Longer Supported"
That's not the same as a quota of zero
"This client is no longer supported" means this sign-in path was shut down on 2026-06-18 — not that you're out of quota. Reinstalling or switching accounts won't fix it.
Four key facts
Date free individual sign-in was shut down
Google shut down Gemini CLI's free/Pro/Ultra individual "Sign in with Google" path on 2026-06-18.
Reinstalling / switching accounts = zero effect
This isn't about your specific account — the entire sign-in path was retired, so reinstalling, wiping config, or trying a different personal Google account won't restore access.
A completely different error from 'client no longer supported'
limit: 0 is a quota-level issue (you can still sign in, you're just out of allotment); 'client no longer supported' means the sign-in path itself is gone, so you never even get to a quota check.
The only path back to access
Per official guidance, the CLI remains accessible via a paid Gemini API key with billing enabled, or the Gemini Enterprise Agent Platform.
What the error text is actually telling you
The full message is "This client is no longer supported for Gemini Code Assist for individuals," shown when signing into Gemini CLI with a personal Google account via "Sign in with Google." It literally means the sign-in method itself has been retired — it's not an account ban and not a quota issue. This free individual sign-in path stopped serving requests for every tier (free, Pro, Ultra) at once on 2026-06-18.
Latest development
Google has moved its free individual terminal offering to the Antigravity platform (desktop app + CLI + SDK + hosted agents); this individual free sign-in path for Gemini CLI will not come back. The CLI binary itself remains usable, but only via a paid Gemini API key with billing enabled, or through the Gemini Enterprise Agent Platform.
Timeline
Google shuts down Gemini CLI's free personal 'Sign in with Google' path, affecting every individual tier — free, Pro, Ultra.
Users are directed to the Antigravity platform, or switch to a paid, billing-enabled API key to keep using the CLI binary.
The 'This client is no longer supported' error keeps appearing for anyone still trying the old personal Google sign-in flow.
Confirmed vs. common misreading
Confirmed
Official Google channels confirm this shutdown affects the 'Sign in with Google' path for every individual tier — free, Pro, Ultra — as of 2026-06-18; the CLI remains usable via a paid API key.
Common misreading
Many people's first instinct is to reinstall the CLI or try a different Google account — neither works, because the entire sign-in path was retired, not a single account or install.
The two errors need completely different responses
limit: 0 (a quota issue)
Your account can still sign in, current quota just shows zero; waiting for the official reset, or checking your account's billing setup, usually resolves it.
client no longer supported (a sign-in path issue)
The free individual sign-in path is retired; waiting does nothing. The only paths forward are a paid, billing-enabled API key, or migrating to an alternative client like Antigravity.
How to tell which one you hit
First check the error text: seeing 'This client is no longer supported' means the sign-in path is gone, not a quota issue. If instead you see a numeric quota field (like limit: 0 or similar), that's a quota-level problem with a completely different playbook. Second, check whether you're using free personal Google sign-in — if so, you've almost certainly hit the 2026-06-18 shutdown.
What to do on QCode
If you just need a terminal-based AI coding assistant to keep working, one QCode key switches straight to Claude Code, Codex, and other tools still offering normal individual access, without waiting for Gemini CLI's personal sign-in to come back.
FAQ
Will reinstalling Gemini CLI fix this?
No. This is a full shutdown of the sign-in path, not a local install or config issue — reinstalling or clearing cache won't restore access.
Will signing in with a different Google account help?
No. Every individual tier — free, Pro, Ultra — lost this sign-in path on the same day, 2026-06-18, regardless of which specific account you use.
Is limit: 0 the same problem?
No. limit: 0 means the account can still sign in and just shows zero quota; 'client no longer supported' means the sign-in path itself is retired — the error happens before you ever reach a quota check.
Is Gemini CLI completely unusable now?
No. The CLI binary remains usable via a paid Gemini API key with billing enabled, or the Gemini Enterprise Agent Platform. Only the free individual sign-in path was shut down.
What should I use instead?
Google has directed individual developers to Antigravity (desktop app + CLI + SDK). If you just need a terminal AI coding assistant, tools like Claude Code that still offer normal individual access are a common migration path.
Is this the same as the quota issues on Codex or Cursor?
No. This is a sign-in path being retired — a product lifecycle change. Codex and Cursor's issues are usage/quota throttling. Both surface as 'it doesn't work,' but the root causes are completely different.
Sources
The 2026-06-18 shutdown of the free individual sign-in path, affecting every individual tier, with the CLI remaining usable via paid API keys — confirmed by public reporting and consistent with our own Google Antigravity 2.0 guide. This page was checked on 2026-08-27.
Personal sign-in gone doesn't mean delivery stops
One QCode key switches to Claude Code, Codex, and other tools still offering normal individual access.
Related reading
Google Antigravity 2.0: the complete guide
Google's official replacement for Gemini CLI — desktop app, CLI, and SDK explained.
Claude Code vs Cursor compared
Another option for a terminal-based AI coding assistant.
How to rotate quota across multiple tools
Sensibly combining access to several AI coding tools.
This page is technical explanation, not an official Google statement. Specific product status and migration paths are governed by official Google channels.