Gemini CLI puts a free agent in your terminal

Google released Gemini CLI: an open-source terminal agent under Apache 2.0, with a free tier that includes a large daily request allowance and access to Gemini 2.5 Pro with its million-token context.

The free tier is the story. This is a competitive move priced at zero.

what it does#

The familiar shape: a terminal agent with filesystem access, shell execution, git awareness, and web search. It reads a GEMINI.md for project-specific instructions. It supports MCP servers for extending its tool set.

npx https://github.com/google-gemini/gemini-cli

Sign in with a Google account and you are running. No API key, no billing setup, no credit card.

why free#

Two reasons, both strategic.

TPU economics. Google serves its own models on its own silicon in its own datacenters. The marginal cost of inference is genuinely lower for them than for anyone renting Nvidia capacity, and they can afford a free tier that competitors cannot match without eating a loss.

Developer mindshare is a leading indicator. The developers who adopt a tool today choose the platform their company standardizes on in two years. Google has lost that fight repeatedly — to AWS in cloud, to OpenAI in AI APIs — and this is a deliberate attempt to not lose it again.

the open source part#

Apache 2.0 on the whole client. That means you can fork it, audit it, run it against a different model endpoint if you rewire it, and inspect exactly what it sends where.

That last one matters more than people acknowledge. A terminal agent has filesystem and shell access. "What does this thing actually transmit" is a question a security team will ask, and "here is the source" is a much better answer than a data processing addendum.

I expect the open-source-ness to be adopted as table stakes. It is very hard to argue for a closed terminal agent when a competitive one is Apache 2.0.

the current state of the category#

By my count there are now four credible terminal-based coding agents from major vendors, plus several from startups, plus a healthy open-source contingent. All shipped within about six months.

They are converging fast on the same feature set: filesystem tools, shell, project instruction files, MCP support, permission prompts, git integration. The differences that remain:

• Model quality on long-horizon tasks, which is the real one.
• Context handling — how they decide what to read and when to compact.
• Permission ergonomics — how annoying the safety prompts are, which sounds trivial and determines whether people turn them off.
• Price, where Google just set an aggressive anchor.

the practical advice#

Try more than one on the same task. They differ more in practice than the feature lists suggest, and the differences show up on tasks that take twenty minutes, not on tasks that take two.

And whichever you use: sandbox it. Container, VM, or at minimum a dedicated user account without your production credentials in its environment. The tooling is good. The failure modes are still real, and "the agent ran a command I did not read carefully" is a bad way to learn that.