Key findings
- Reliability is the most reported concern. 25 of the 27 accounts that discuss it raise it as a problem, describing loops, capacity errors, and edits that broke working code.
- Large context and the open, extensible design draw the most consistent praise. All 11 accounts on context and all 12 on extensibility are positive.
- Of 31 authors who compared Gemini CLI with another agent they also used, 22 judged it behind and 9 judged it competitive.
- Team accounts give Gemini CLI narrow jobs, such as generating payment adapters or headless runs across many repositories. Since June 2026 their posts turn to model access and whether Google will keep investing in the tool.
- Of the accounts that still apply, 24 were published after June 18, 2026 and 17 earlier ones cover workflow and settings. 41 need a recheck and 7 are out of date.
Give Gemini CLI scoped jobs that end in a test or a pull request, and retest its reliability on your own repositories before a wider rollout. Of the accounts GILD read, published from June 25, 2025 to October 27, 2026, 41 still apply as written. Gemini CLI has served only paid sign-ins since Google moved free, Google AI Pro, and Google AI Ultra users to Antigravity CLI on June 18, 2026.
Who wrote the 89 accounts
The 89 accounts are 68 community posts and comments, 44 from Hacker News, 17 from GitHub, 4 from Reddit, and 3 from X. There are also 21 blog posts and reviews, one of them a Google case study. Each names its author, links its page, and records the plan, model, or version where the author states one.
71 accounts come from individual builders. Eighteen speak for a team or an organization: eleven professional teams, three small teams, three technical leadership accounts, and one organization-wide account. Product direction is the only theme the team accounts raise often enough to count, so read the team accounts below directly.
What still applies after June 18, 2026
Early accounts often credited free access, 1,000 requests a day with a personal Google account. Google withdrew that access on June 18, 2026. GILD marks as Out of date the 7 accounts whose main point rests on it or on a personal Google AI plan, and counts them in no theme.
41 accounts need a recheck because they describe Gemini 2.5 or early Gemini 3 models, automatic fallback from Pro to Flash, or quota and bug behavior from before the change. Their reports of loops and rate limits match later accounts. Retest each under a Code Assist subscription or Vertex AI billing before it informs a decision.
17 earlier accounts still apply as written, because they describe workflow, settings, or automation that work the same on paid sign-ins. Alexandre Touret used a Code Assist organization license, Paulo Henrique worked from a plan file and GEMINI.md rules. The author of AgentCommander runs Gemini CLI headless as the backend for their workflow engine.
Where teams put it to work
In a case study Google published, Inspired Entertainment gives Gemini CLI operator API documentation and its own guidelines to write payment adapters, and reports 5 dev days per integration, down from 40.
In September 2026, a team running Gemini CLI headless across many repositories found that Gemini 3.5 Flash was silently answering requests for newer model IDs. The CLI raised no error and exited with code 0. They caught it only by diffing --debug output against what they had asked for.
The most recent company accounts are critical. Code Assist Enterprise customers report waiting weeks for Gemini models that Antigravity received on release day. Two teams moved to Claude outright, and at a third company the Workspace renewal rose about 50 percent while the team paid extra for Claude.
- Scope each use to a job with a check, such as a pull request or a test suite.
- Decide the sign-in route before engineers start.
- Confirm which model served each run, with /stats or --debug output.
- Keep a human reviewer and an undo path on every change the agent makes.
What to test in a pilot
Retest reliability on your own repositories with a stop rule for sessions that loop. Measure requests per task against the daily cap of 1,500 per user on Code Assist Standard or 2,000 on Enterprise. Lock the sandbox and YOLO mode in system settings before the pilot starts. Run Antigravity CLI on the same tasks, because Google stopped selling new Code Assist subscriptions on October 9, 2026 and points teams to Antigravity through Gemini Enterprise.
Methodology
GILD opened every account on October 12, 2026, and 7 more on October 25, 2026, each with a verbatim quote. For every account it recorded its author, publisher, publication date, who it speaks for with a verbatim excerpt, overall sentiment, evidence kind, and the positions it takes. The record format matches the one GILD uses for Claude Code. Hacker News comments were read through the Hacker News API, GitHub issues and discussions through the GitHub API, Reddit posts through the Arctic Shift archive, and posts on X through FxTwitter. A GitHub issue that reports a bug counts as mixed unless its author rejects Gemini CLI. GILD left out Google employees writing about their own product, news write-ups, command-list tutorials, coding-tool vendors' comparisons, and pages not written in English. Talks and podcasts were checked and left out because none gave a readable, attributable account of use by someone outside Google. GILD counts a theme only when at least 5 accounts from 3 different authors discuss it. The counts describe these 89 public accounts.
Products in this piece
Sources
- Official documentation
- 5
- Public source
- 13
- Google Developers Blog: Transitioning Gemini CLI to Antigravity CLI (May 19, 2026)
- Gemini Code Assist docs: Gemini Code Assist Standard and Enterprise subscriptions
- Gemini CLI docs: Quota and pricing
- Gemini CLI docs: Enterprise configuration
- Gemini Code Assist docs: Gemini CLI
- Google Developer forums, a Google case study: Inspired Entertainment generates payment adapters with Gemini CLI (Jul 20, 2026)
- Alexandre Touret: Streamlining development with Gemini CLI, a hands-on review (Sep 1, 2025)
- Paulo Henrique, DEV Community: With Gemini CLI, I'm able to keep my pet projects alive and kicking (Mar 3, 2026)
- Simon Willison: Gemini CLI (Jun 25, 2025)
- The New Stack, David Eastman: Expectations for agentic coding tools, testing Gemini CLI (Jul 7, 2025)
- XDA Developers: I tried out Google's new Gemini CLI (Aug 1, 2025)
- Sanket Gawas: Free vs Premium, testing Gemini CLI against Claude Code (Jul 18, 2025)
- Nek.12: I spent 400 hours working with AI agents (Dec 1, 2025)
- Sakib Sadman Shajib: Porting codex-plugin-cc to Gemini CLI (Apr 14, 2026)
- Edward Ramos: Building AI-assisted workflows for Angular modernization (Sep 11, 2026)
- GitHub comment by Gerry Burde: newer model IDs silently served by Gemini 3.5 Flash (Sep 5, 2026)
- GitHub issue 28625: Enterprise Gemini CLI users waiting for Gemini 3.5 and 3.6 Flash (Aug 2, 2026)
- GitHub discussion 27274: user comments on the Antigravity CLI transition (May to Jul 2026)