google-gemini/gemini-cli

Adopt with caution: the README states that unpaid-tier and Google One users were moved to Antigravity CLI on June 18th, 2026, and that the current release is not optimized for the newest Gemini models. That changes the decision from "which terminal agent?" to "is this still the right tool for my setup?"

The problem

A developer working in a terminal wants an assistant that does more than autocomplete: read the repository, propose edits across files, run tests and shell commands, and explain what failed. Without an agent in the terminal, that becomes repeated trips between editor, chat window and shell. Gemini CLI puts that loop in one CLI session, so the user stays in the same directory and approves or rejects changes as they come.

What's different

The project is a TypeScript agent whose topics include MCP client and server, so it can be wired into the Model Context Protocol ecosystem. The documented setup offers several paths: global npm, Homebrew, MacPorts, and an Anaconda route for restricted environments. Organizations with a paid Code Assist license set GOOGLE_CLOUD_PROJECT before launching, which means the project ships an enterprise credential path, not only a hobbyist CLI.

The most important trade-off is support status. The README says Gemini CLI is not optimized for Gemini 4 Argon and directs users to Antigravity for the best coding experience. It also documents the transition for free and Google One users. The installation guide holds recommended specifications and is worth reading before committing.

Who should try it

It fits a developer with a terminal-heavy workflow who wants a Gemini-backed agent inside it, especially someone with an organizational Code Assist license following the documented project setup. It also fits people experimenting with MCP-connected tools who want a CLI agent.

It is a poor fit for someone starting fresh with Gemini models and expecting the current best coding experience, since the README sends those users to Antigravity CLI. Unpaid-tier users wanting a long-lived setup should check the replacement first.

Requirements and limitations

Installation assumes Node.js and npm for the main path, with Homebrew, MacPorts and conda as alternatives; conda is explicitly for restricted environments. Organizational users need a paid Code Assist license and the Google Cloud project variable. Free-tier and Google One usage is constrained by the documented transition, and the README says the tool is not optimized for Gemini 4 Argon.

Upkeep is mainly version and model alignment: installation, execution and releases are split across docs, so users should track those pages. Bugs can be reported through /bug.

HotRepo's take

HotRepo recorded only two daily-board dates, 2026-10-24 (+38 stars) and 2026-10-25 (+44 stars), which is insufficient to judge whether interest is rising, fading or sustained. The repository is about 555 days old; a 303-point Hacker News thread on 2026-01-22 concerns a label-removal incident, not product quality.

The decision-relevant point is the README's own transition notice: verify your account tier and whether the replacement covers your workflow.