Gemini CLI review: README vs what users report
Gemini CLI puts a Gemini-powered agent straight into your terminal, with shell commands, file edits, and Google Search grounding built in rather than bolted on. Reach for it if you're already on a Google account and want a free, terminal-native coding assistant; skip it if you need multi-provider models or session memory that persists without manual checkpoints.
The README of google-gemini/gemini-cli puts a warning box above the install commands, and that box rewrites what the one-line description promises. The description still calls the project an open-source AI agent that brings Gemini into the terminal. The box says the tool is now aimed at organizations with Gemini Code Assist Standard or Enterprise licenses, that free individual access and Google AI Pro and Ultra accounts moved to Antigravity CLI on 2026-06-18, and that it is not tuned for the Gemini 4 series or for benchmarking Gemini models.
Claim one, open source: this holds on paper. The license is Apache-2.0, and commits are still arriving (the newest push is dated 2026-11-10), and 726 open issues sit against 108,765 stars. Quality is where the commenters push back. On Hacker News, @tempest_, 2026-04-29 wrote "The gemini-cli repo is gong show too". Over a month later, @tempest_, 2026-06-02 said they understand the complaints in a linked GitHub discussion but still find the situation hilarious, and called the repo perhaps one of the best worst examples of 'opensource' LLM development. That is one person speaking twice, so it counts as one voice, not two.
Claim two, a working terminal agent: here the comments and the README diverge. @agluszak, 2026-05-07 wrote "Meanwhile Gemini CLI has been broken for months!", and @kakugawa, 2026-03-31 wrote that "gemini-cli has not been useable for weeks.", adding that the endpoint used for subscription users was rate-limited to the point of being non-functional. Both comments predate 2026-06-18, the day the README says free and Pro/Ultra access left for Antigravity CLI, kakugawa's complaint concerns the endpoint for subscription users, and agluszak does not say which setup was broken. None of the supplied comments says whether the enterprise path behaves the same way.
Claim three, the account split: @hsaliak, 2026-02-28 wrote "The Gemini-CLI situation is poor." and said it was not communicated early that AI Pro or AI Ultra accounts cannot be used with this API broadly. The README now states account eligibility at the top, which is the topic hsaliak raised, but the supplied text of that comment ends mid-sentence, so it is unclear whether the two describe the same restriction.
The evidence is thin: four people, all on Hacker News, all dated before the README's 2026-06-18 transition. The box also says nothing about rate limits or reliability, the two things these commenters complained about.
Related repositories
Still deciding about gemini-cli?
One click hands the question to an AI along with this page โ see what it says about gemini-cli.
