Updated November 12, 2026: our earlier Gemini CLI pricing guide incorrectly recommended consumer free access and Google AI Pro/Ultra as current CLI options. Those consumer routes stopped serving requests on June 18. New Gemini Code Assist Standard and Enterprise subscription sales also closed on October 9. This correction preserves the original URL and publication date.
What changed, and what should you buy now?
Google's dated consumer deprecation notice covers Gemini CLI as well as the Code Assist IDE extensions. It directs affected users toward Antigravity. Do not buy a consumer plan expecting the old Gemini CLI daily-request allowance.
There is a separate business subscription timeline. New Standard/Enterprise purchases ended October 9. Existing Code Assist contracts remain supported through their applicable contract terms; annual renewals end after January 31, 2027, and monthly renewals after December 31, 2027. Existing Gemini Enterprise Code Assist entitlements continue until March 31, 2027. Check which agreement you actually hold before making a migration plan.
API access is a separate decision
The CLI authentication guide documents Gemini API-key and Vertex AI routes. These are distinct from consumer account entitlements. Technical support for a route does not mean every model has free quota, unlimited throughput or a fixed monthly price. Confirm current model access, regional eligibility and billing in your own project.
Some generic authentication instructions still describe personal Google sign-in. For the discontinued consumer offering, the newer, explicit deprecation notice takes precedence. We do not treat those older instructions as evidence that the retired consumer quota is available again.
A practical decision table
| Your situation | Next step |
|---|---|
| Former consumer CLI user | Evaluate Google's documented Antigravity migration route rather than upgrading for the old CLI quota. |
| Existing business subscriber | Confirm contract and renewal dates with your administrator; plan a bounded migration test. |
| API-based automation | Verify the selected API model and project billing, then measure actual task costs. |
| New team procurement | Do not budget a new Code Assist Standard/Enterprise purchase that is no longer sold. |
How to budget token-billed coding work
Start with the total cost of a completed task, not the first model response. Repository exploration, repeated context, tool results and retries can make two apparently similar tasks consume different amounts. API quotas can still apply even when billing is enabled; pay-as-you-go should not be described as unlimited access.
For a controlled evaluation, select representative tasks and define what counts as accepted work before running them. Record billed input and output, any separately billed tools, task completion, reviewer time and timeouts. Keep failed attempts in the totals.
A hypothetical run costing $8 for four accepted changes has a $2 inference cost per accepted change. If two additional failed attempts cost another $4, the experiment's real inference cost per accepted change becomes $3. This is a budgeting example, not a Gemini rate or performance claim. Add human review and infrastructure if comparing the total operating cost.
Make migration a test, not a leap
Inventory the commands, extensions, permission rules and automated jobs your team relies on. Trial the replacement on a noncritical repository with approved data and a hard budget. Compare accepted work and review effort against the current workflow rather than comparing brand names or headline request quotas.
Keep the old working configuration recoverable while testing. Do not copy credentials or broad tool permissions blindly into another agent. Check data handling, secret storage and command approval behavior before running against production systems.
What to monitor after choosing a route
- Cost per accepted task and the proportion needing human repair.
- Quota failures, retry counts and peak parallel usage.
- Model and plan changes that alter the original budget.
- Contract deadlines and whether a renewal is actually available.
The right pricing answer in November 2026 begins with eligibility. First establish which product and access route are available to you; then compare total cost and useful output. The old consumer quota table is not a current buying guide.