The argument in one line.
Gemini CLI excels at adding features to existing codebases with context but fails at generating visually compelling projects from scratch without sufficient architectural guidance.
Read if. Skip if.
- A developer working in an existing codebase who wants to quickly test whether Gemini CLI can handle real maintenance tasks like bug fixes and feature builds.
- A developer evaluating free AI CLI tools and needs a straightforward comparison of Gemini CLI's actual performance against its advertised capabilities and rate limits.
- A terminal-first developer already familiar with Claude Code or similar tools who's curious whether Google's free tier makes switching worth considering for incremental coding work.
- You're building greenfield projects or starting from scratch — the video concludes Gemini CLI fails on new projects with no existing context.
- You need to evaluate enterprise-grade or production-ready AI tooling — this tests the free tier at hobbyist scale, not paid plans or reliability guarantees.
- You're comparing IDE-integrated tools like Cursor or Gemini Code Assist — this breakdown focuses exclusively on terminal-based CLI usage.
The full version, fast.
Google's Gemini CLI is a free terminal-based AI coding agent that ships with Gemini 2.5 Pro, a 1M-token context window, 60 requests per minute, and 1,000 requests per day at zero cost, plus built-in Google Search, MCP server support, and a customizable GEMINI.md memory file. Three live tests reveal where it actually delivers: a one-line CSS scrolling fix passed instantly, and a medium-sized build adding a full memory feature with database migration, schema changes, new UI page, and API integration completed in minutes for three cents in tokens. A from-scratch Next.js landing page failed even after iteration, producing flat visuals. The rule for you: lean on Gemini CLI inside existing codebases where context is rich, not on greenfield projects.
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Create a free account →Where the time goes.

01 · Cold open — direct competitor, completely free
Talking-head intro promising the breakdown: what makes Gemini CLI special, how to set it up, and three real-world coding tests.

02 · Gemini CLI announcement — open source AI agent for your terminal
Walks through Google's launch blog post. Open-source CLI for the terminal, two modes (interactive REPL + single-shot prompt), mentions Gemini Code Assist as Google's Cursor competitor. Frames Google as 'AI everywhere developers are.'

03 · Free-tier breakdown — the price-objection killer
Full-screen card: 60 req/min, 1,000 req/day, Gemini 2.5 Pro (1M context), Open Source, Available free-of-charge. Brandon does the math: a single 1M-context request would cost $3 on the API; he just gave you $180/day for free.

04 · Major features tour + setup
Built-in Google Search from the terminal, MCP server support (image-gen + Veo video gen demo from launch post), GEMINI.md custom prompt file, scripting/automation. Then setup: npm install -g @google/gemini-cli, run gemini, log in with personal Google account for free tier, or paste GEMINI_API_KEY into .env to bypass limits. Tours /version, /theme, /editor, /tools slash commands.

05 · Case 1 — Simple code fix (PASS)
Real bug: profile page won't scroll, content cut off at the bottom. Brandon @-references the file, Gemini investigates, proposes a CSS overflow fix, opens the diff in his external editor (Cursor) for review, applies. Then he teaches Gemini a project rule on the fly: 'only run npm lint, never run npm run' — update memory — Gemini writes it to GEMINI.md so the rule persists. Verdict: clean pass.

06 · Case 2 — Medium task: full Memories feature (BIG PASS)
Adds an entire new Memories tab to his ShipKit chat template: new sidebar entry, CRUD page, Postgres schema migration, API changes so every chat injects memories into the system prompt. Uses an AI-driven workflow — screenshot + task_template.md + GEMINI.md as context, asks Gemini to plan first, reviews the multi-phase plan, requests Phase 0 (schema), then implements phase by phase. Gemini lints between steps, fixes its own errors, ships working feature in minutes. End-to-end test in-app: types a memory, sends a chat, response respects it. Verdict: massive pass.

07 · Case 3 — Hard test: new landing page from scratch (FAIL)
Empty folder, .env with API key. Prompt: build a Next.js landing page for the AI With Brandon channel, look me up on YouTube first, make it beautiful and modern. Gemini researches the channel, drafts copy. Hits a wall trying to run create-next-app interactively (CLI wizards confuse it) — Brandon escapes, runs npx manually, hands the scaffolded project back. Gemini styles it, but the result is generic and ugly. Second pass with a screenshot + 'do not stop until it's absolutely beautiful' — slightly better, still underwhelming. Verdict: fail. 'Gemini CLI thrives with context, struggles without it.'
Lines worth screenshotting.
- Gemini CLI's free tier — 60 requests per minute, 1,000 requests per day, Gemini 2.5 Pro, 1M context window, $0 — is not a trial; it is a permanent tier that makes professional-grade AI coding available without a subscription.
- The 1M token context window is Gemini CLI's structural advantage: it can load an entire large codebase into a single session where Claude Code would need to navigate selectively.
- Gemini CLI thrives on existing codebases and fails on greenfield projects — the inverse of what most developers assume, and the rule that determines where it belongs in a multi-tool workflow.
- A full memory feature with database migration and UI built correctly in a single Gemini CLI session is not a simple task — it is the category of work that justifies using a tool with deep codebase context over a tool that generates from scratch.
- Generating a from-scratch Next.js landing page without existing code context is where Gemini CLI produces generic, usable-but-not-good output — which is the accurate boundary test that separates demo conditions from production conditions.
- Gemini CLI is open source, which means the rate limits and free tier are not a marketing hook that disappears in six months — they are baked into a product with a public repository that anyone can inspect.
- The correct use case framing for Gemini CLI vs Claude Code is not 'which is better' but 'which task has more existing context to work from' — Gemini wins when context is rich, struggles when context is empty.
- A simple one-line CSS fix handled correctly by Gemini CLI confirms the floor: it can do the easy stuff reliably, which is the prerequisite before trusting it with the medium-complexity work.
- Google releasing a Claude Code competitor for free is a competitive pressure event that will force Anthropic to either match the free tier or differentiate on quality — neither outcome is bad for users.
- 60 requests per minute is a high enough rate limit to run Gemini CLI in agentic loops that make multiple tool calls per task without hitting the ceiling during a normal work session.
- The right workflow for teams is Gemini CLI for existing codebase work and a generative tool for greenfield — splitting by task type rather than choosing one tool eliminates the failure modes of each.
- A terminal-based coding agent from Google authenticating through an existing Google account removes the API key setup friction that stops non-technical users from starting.
- The medium-complexity test — a feature that required database migration logic, backend integration, and frontend UI — being handled correctly in one session is the result that matters most for real-world adoption decisions.
- Greenfield project failure is not a model quality issue; it is a context issue — the model has no existing patterns, no naming conventions, no architectural decisions to build on, so it produces generic output.
- The honest three-test verdict format — one pass, one pass, one fail — is more useful than a demo that only shows the tool succeeding, because it tells you exactly where the boundary is before you find it yourself in production.
Gemini CLI Is Free and Extraordinary — With Enough Context
Brandon Hancock's three-test review shows that Gemini CLI thrives on structured context and multi-phase plans but fails at open-ended from-scratch builds where it has to make aesthetic and architectural decisions without guidance.
- Direct Claude Code competitor, completely free — three real-world tests to find where it passes and where it fails
- 60 requests per minute, 1,000 per day, Gemini 2.5 Pro, 1M context window — completely free with a personal Google account
- A single 1M-context API call costs $3 — the free tier delivers $180 per day of compute at zero cost
- GEMINI.md is the persistent project rules file — the equivalent of CLAUDE.md for Gemini CLI sessions
- MCP server support enables image and video generation directly from the terminal
- CSS overflow fix with the file referenced is a clean pass — at-reference the file, let Gemini investigate, review the diff
- Teaching a project rule on the fly — only run npm lint — and watching Gemini write it to GEMINI.md is the memory workflow in action
- Screenshot plus task template plus GEMINI.md as context, plan first, implement phase by phase — this workflow produced a working full-feature build
- Gemini linted between phases and fixed its own errors — the structured workflow is what enabled the clean execution
- Empty folder plus open-ended prompt produced generic output — no context means no quality
- Interactive CLI scaffolding broke the agent — run scaffolding commands manually and hand the project back rather than having Gemini attempt interactive terminal wizards
Terms worth knowing.
- CLI (Command Line Interface)
- A text-based way to control software by typing commands into a terminal instead of clicking through a graphical interface.
- Gemini CLI
- Google's open-source AI coding agent that runs inside a terminal, letting developers chat with Gemini models, edit files, run searches, and execute tasks from the command line.
- Claude Code
- Anthropic's terminal-based AI coding agent that reads, writes, and edits files in a project through natural-language conversation. Often cited as the direct competitor to Gemini CLI.
- Interactive mode
- Running a CLI tool as an ongoing chat session where you can send multiple messages, see streaming output, and approve actions, rather than firing one isolated command.
- Single-shot request
- Calling an AI tool with one self-contained prompt that returns an answer and exits, rather than starting an ongoing conversation.
- Cursor
- An AI-first code editor built as a fork of VS Code, with chat, inline edits, and codebase-aware suggestions powered by large language models.
- Gemini Code Assist
- Google's in-IDE AI coding assistant that adds chat, inline edits, and file-aware suggestions to editors like VS Code and JetBrains. Positioned as Google's competitor to Cursor.
- Gemini 2.5 Pro
- Google's flagship large language model at the time of the video, featuring a one-million-token context window and strong reasoning, coding, and multimodal capabilities.
- Context window
- The maximum amount of text, measured in tokens, that a language model can consider in a single request, including both the prompt and its response.
- Token
- The basic unit of text a language model processes, roughly equivalent to a short word or word fragment. Pricing and context limits are measured in tokens.
- MCP (Model Context Protocol)
- An open protocol that lets AI agents connect to external tools and data sources, such as image generators, Notion, or Gmail, through standardized server interfaces.
- MCP server
- A small program that exposes a specific tool or data source to an AI agent over the Model Context Protocol, allowing the agent to call its functions during a session.
- Veo
- Google's generative video model, used here through an MCP server to turn a still image into a short AI-generated video clip.
- GEMINI.md
- A markdown file placed in a project that Gemini CLI loads as persistent context, used to store project rules, conventions, and instructions the agent should follow on every run.
- npm
- The standard package manager for Node.js, used to install JavaScript libraries and command-line tools globally or per project.
- Node.js
- A JavaScript runtime that lets developers run JavaScript outside the browser. Required to install and run many modern CLI tools.
- Global install
- Installing a package system-wide rather than into one project, so its command can be invoked from any directory in the terminal.
- Workspace account
- A Google account managed by an organization through Google Workspace, distinct from a personal Gmail account and often subject to different access policies.
- API key
- A secret string that authenticates requests to a paid service, letting the provider track usage and bill the account that owns the key.
- .env file
- A plain-text configuration file holding environment variables such as API keys, kept out of source control and loaded by an app at runtime.
Things they pointed at.
Lines you could clip.
“If you ran 60 of those massive requests, you're easily getting up to a $180 worth of tokens from Gemini 2.5 Pro completely for free.”
“I never wrote a single line of code. I added in a whole new feature, database change, UI change, and updated API calls, and it worked in under two minutes.”
“Gemini CLI thrives with context, and without context, it's struggling.”
“Use Gemini CLI on your existing projects to add in new features and small changes. I would not recommend it right now for creating brand new projects.”
Word for word.
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
The bait, then the rug-pull.
Brandon Hancock opens face-cam in front of an American flag and a bookshelf and lands the same three nails Google itself led the launch with: direct competitor to Claude Code, insanely powerful, completely free. Then he promises the only thing a developer actually wants — three real coding tests, no demos, watch it succeed and fail in real time.
Named ideas worth stealing.
Three-Test Verdict Format
- Simple test (1-line fix) — proves baseline reliability
- Medium test (multi-file feature with DB) — proves real workflow value
- Hard test (greenfield project) — finds the breaking point
Brandon's review structure: escalating-difficulty live coding tests, each with an explicit pass/fail call. Lets the viewer make their own verdict without trusting his opinion.
AI-Driven Task Development Loop
- Maintain a task_template.md (project shape, tech stack, conventions)
- Maintain a GEMINI.md (project rules + memory, updated continuously)
- For each feature: take screenshot + reference task_template.md, ask Gemini for a multi-phase plan first
- Review the plan, request edits (e.g. 'add a Phase 0 for schema changes')
- Have Gemini generate a long-form task doc in /ai_docs/
- Execute phase by phase, review between phases
- When Gemini makes a mistake, add a rule to GEMINI.md so it never repeats
Brandon's whole AI coding workflow, taught in passing inside the Case 2 demo. The pattern (template + context file + plan-then-execute) is portable across any agentic CLI.
Update Memory pattern
When Gemini makes a mistake, say the correction out loud and add the words 'update memory'. Gemini writes the rule into GEMINI.md automatically. Use /memory show to view all current rules.
Free-Tier Value Math
Don't just list specs — convert them to dollars-per-day. 60 req/min × 1M-context Gemini 2.5 Pro at $3/req = $180/day in free tokens. Concrete dollar value kills the 'is this real?' skepticism in one sentence.
How they asked for the click.
“I have a ton of other AI related content right here on this channel. Everything from agent development kit, LangChain, CrewAI, Next. Js. I have it all right here, and I definitely recommend checking out those videos and whichever video is popping up right now on the screen.”
Soft channel CTA at the end — no hard ask for likes, no link drop, just 'next video is on screen.' Honest video earns the trust to skip the hard sell. The real sales pitch is the ShipKit.ai mention woven into Case 2 as the codebase being demoed.









































































