Gemini · Local terminal agent
Product and access
Gemini CLI is Google's terminal-based agent for local development work. MCP, extensions, and skills supplement its built-in tools.
Core features
6 features from provider sources · sources reviewed on September 30, 2026. Availability and limitations are listed directly below.
Use shell and web tools
The agent can run shell commands and search for information using built-in tools.
Source 1Connect MCP servers
MCP provides additional tools, resources, and prompts through local or remote servers.
Source 2Load extensions and skills
Extensions bundle configuration and tools; Skills provide task-specific instructions and resources.
Source 4Approve tool calls
File changes and shell commands are assessed according to security policies and may require confirmation.
Source 1Revert changes using a checkpoint
Optionally saved project and conversation states can be restored with the restore command.
Source 5
Requirements and limits
‘Still open’ means the reviewed sources do not answer this point clearly.
Requirement
Local requirements and internet access
Installation requirements include a supported operating system, Node.js, a shell, and internet access.
Source 6Limitation
Sandbox depends on configuration
Sandboxing must be configured for the platform; additional paths or network access may require separate approvals.
Source 3Limitation
Checkpoints are disabled by default
Checkpoint recovery is available only after it has been enabled in the configuration.
Source 5
Practical tasks
Editorial examples based on documented features. No product tests performed.
Make a small change in the terminal
- Your input
- A local repository, project rules, and a narrow acceptance criterion.
- Possible result
- A traceable diff with completed checks.
- What to check
- Review suggested commands, file changes, and test results.
Use a project tool through MCP
- Your input
- A reviewed MCP server, minimal credentials, and a specific task.
- Possible result
- A structured tool call with a result in the CLI context.
- What to check
- Check the server source, shared tools, arguments, and external effects.
Implement a small code change in the terminal, run the appropriate tests, and review the diff.
Your possible prompt
Read the project rules. Investigate [error], propose a small change, and run the relevant checks. Show me the diff and any remaining uncertainties.
Getting-started idea based on documented capabilities. Not an executed product test. Adapt the task, data, and permissions.
What you should know first
Current official Gemini CLI documentation. Security behavior and available features depend on local configuration, version, and access.
Requirements & limitations
Configure tool permissions, sandbox, and project access carefully. Review changes, commands, and external MCP servers before approval.
Setup
Set up Node.js, Gemini CLI, supported access, and a project directory.
Pricing model
Check access / usage. Check current terms and included quotas with the provider.
The classification indicates the scope of effort. It is not a price or performance commitment.
Sources from the provider
Editorial team: Michael Meierhoff · sources reviewed on . Provider information is not independent evidence of performance.
-
geminicli.com /docs/reference/tools/
-
geminicli.com /docs/tools/mcp-server/
-
geminicli.com /docs/cli/sandbox/
-
geminicli.com /docs/cli/using-agent-skills/
-
geminicli.com /docs/cli/checkpointing/
-
geminicli.com /docs/get-started/installation/
