Gemini CLI Guide
Google’s open-source terminal agent for Gemini, project context and command-line automation.
Last verified: · How we verifySuitable workflows
Developers using Google accounts, Gemini API keys or Vertex AI.
Limitations and billing
Quotas depend on authentication. Workspace accounts may need a Google Cloud project.
Capabilities we verified
This is an evidence-based shortlist, not an exhaustive feature inventory. Omitted capabilities have not been checked for this record.
Pricing & usage
Free access; see limits
Account quota or metered Gemini / Vertex AI usage. The cost of metered usage or an external agent can be separate from the subscription.
Check official pricing ↗Models & access
Google sign-in, Gemini API key, or Vertex AI credentials.
Verified families: Gemini.
Official model information ↗Install and start the CLI
Install a supported Node.js version and npm; use the stable release for normal projects.
Installation command · npm
npm install -g @google/gemini-cliOpen your project folder in a terminal, then run:
geminiAccount and authentication
Choose Google sign-in, GEMINI_API_KEY, or Vertex AI on first launch.
Project configuration and tools
Use GEMINI.md for project context; configure extensions and MCP separately from authentication.
First task to try
Map the main modules and test commands before asking Gemini to change a file.
Script usage
This example asks for a project summary. Tool permissions still apply; a prompt is not a sandbox.
gemini -p "Summarize the project structure without modifying files."Related CLI tools
All AI CLI tools →
Project evaluation checklist
- Open a small, familiar project and confirm that your essential language tooling works.
- Give the agent one bounded change with an observable acceptance criterion.
- Review the diff, run the project’s checks and compare the result with your current workflow.
- Inspect usage after the task. Estimate a month of similar work, including any separate model or agent bill.