Who can still use Gemini CLI
Most “Claude Code vs Gemini CLI” articles still describe Gemini CLI as the free alternative, with a generous daily allowance on a personal Google account. That stopped being true on June 18, 2026.
In a May 19, 2026 announcement, Google said Gemini CLI and the Gemini Code Assist IDE extensions would stop serving requests for:
- free users (Gemini Code Assist for individuals)
- Google AI Pro subscribers
- Google AI Ultra subscribers
Those users were moved to Antigravity CLI. Gemini CLI keeps working for:
- organizations with a Gemini Code Assist Standard or Enterprise license, whose access is unchanged
- anyone using a paid Gemini API key or a Gemini Enterprise Agent Platform API key
Gemini CLI is still actively developed: its repository gets commits almost daily and ships nightly and preview releases. But its README now says it hasn’t been optimized for Gemini 4 Argon and recommends Antigravity for that model.
So the real question depends on who you are:
- An individual developer choosing a terminal agent: compare Claude Code with Antigravity CLI or a model-agnostic agent. Gemini CLI now means paying per token.
- A team on Google Cloud with Code Assist licenses: Gemini CLI is a solid option you already pay for.
The key difference
Both are terminal-first coding agents. They read your repository, edit files, run commands and tests, and can run without supervision in scripts and CI (claude -p for Claude Code; Gemini CLI’s non-interactive mode).
The differences that decide it:
- Openness. Gemini CLI is Apache-2.0 open source: you can audit it, fork it, or build an internal agent on top of it. Claude Code is closed source.
- Models. Each one is tied to its vendor’s models. Claude Code runs Claude (directly, or through Amazon Bedrock, Google Cloud or Microsoft Foundry); Gemini CLI runs Gemini.
- Where it runs. Claude Code is one agent across several surfaces: the terminal, VS Code and JetBrains extensions, a desktop app, and cloud sessions in the browser. Gemini CLI is a CLI with a VS Code companion extension, and it connects to JetBrains IDEs and Zed through the Agent Client Protocol.
- How you pay. Claude Code is a flat subscription with usage limits. Gemini CLI is either a per-user organization license or per-token API billing.
Pricing in practice
| You are… | Claude Code | Gemini CLI |
|---|---|---|
| An individual developer | Pro, $20/month ($17/month billed yearly); Max 5x $100 or Max 20x $200 for heavier use | No plan for individuals since June 18, 2026; pay per token with a paid Gemini API key |
| A team | Team plan: Standard seat $25/user/month ($20 billed yearly), Premium seat $125 ($100 billed yearly) | Gemini Code Assist Standard $22.80/user/month ($19 on a 12-month commitment), Enterprise $54 ($45) |
| Paying per token | Anthropic API key, billed by usage | Paid Gemini API key, billed by usage |
Prices are from the official Claude pricing and Gemini Code Assist pricing pages, checked October 22, 2026. Google lists Code Assist prices as hourly rates; the monthly figures above are those rates over a 730-hour month.
For an individual, Claude Code Pro gives predictable cost: you know the monthly bill and the usage limits. Per-token billing in Gemini CLI can be cheaper for light, occasional use and more expensive for long sessions.
Features side by side
Where they’re the same:
- Both connect to MCP servers.
- Both support hooks and subagents.
- Both read a project instructions file:
CLAUDE.mdandGEMINI.md. - Both run headless for automation.
- Both work on macOS, Windows and Linux. Gemini CLI’s docs list macOS 15+, Windows 11 24H2+ and Ubuntu 20.04+, and it needs Node.js 20+.
Where they differ:
- Extensibility. Claude Code adds skills and plugins on top of MCP, hooks and subagents. Gemini CLI has its own extensions system.
- Surfaces. Claude Code’s desktop app and browser sessions let you hand off a task and check back later. Gemini CLI stays in the terminal and your IDE.
- Customization. Being open source, Gemini CLI can be changed at the code level. Claude Code can only be extended through its plugin points.
Who should pick which
Choose Claude Code if:
- you’re an individual developer who wants a fully supported terminal agent at a fixed monthly price
- you want the same agent in your terminal, editor, desktop app and browser
- you’re happy to use Claude models only
Choose Gemini CLI if:
- your organization already has Gemini Code Assist Standard or Enterprise licenses
- you need an open-source agent you can audit, fork or embed in internal tooling
- you’re on Google Cloud and prefer per-token billing on a paid API key
Look elsewhere if:
- you were using Gemini CLI for free: Google’s path is Antigravity CLI
- you want to switch between Claude, Gemini and other models in one tool: see OpenCode or Cline
Using both on one project
Nothing stops you running both in the same repository. Some teams use one agent to write a change and the other to review it. The friction is instructions: Claude Code reads CLAUDE.md and Gemini CLI reads GEMINI.md. Keep shared conventions in one file and reference it from both, so the agents follow the same rules.
Hands-on test
We haven’t run a hands-on test of this pair yet. This comparison is based on each vendor’s documentation, pricing pages and repositories, linked on the Claude Code and Gemini CLI pages. When we add a test, this page will name the task, the tool and model versions, and the date it was run.
