Agent Atlas / Coding agents

google-gemini/gemini-cli

A terminal-first coding agent whose public source exposes tool scheduling, hooks, policy, context assembly, extensions, and specialized workers.

Coding agent CLI Full dossier Reported + sourced Reviewed July 21, 2026
Intended operator

Developers operating an agent in a terminal or through an integrating client.

Primary surfaces

terminal client / built-in tools / MCP and extensions

Tracked repository

google-gemini/gemini-cli

Teaching mechanism

Hooks can add context or stop work before execution

BeforeAgent and related hook boundaries let the runtime attach delimited context or block a run before the next agent step.

Evidence limitA documented hook boundary does not establish that every extension is safe or that every client exposes the added context.
Inspect the source

System Map

Eight inspection boundaries
Model boundary

The CLI assembles provider requests and tool declarations around the selected Gemini or compatible model path.

Context and memory

Workspace files, conversation state, settings, hooks, and extension context can shape the model-visible request.

Tools and execution

Built-in file, shell, web, and MCP tools pass through scheduler and policy code.

Permissions and isolation

Approval modes, policy checks, trusted folders, and sandbox options separate a proposal from an allowed effect.

Sessions and recovery

Session and tool lifecycle state support resumption, cancellation, and visible failure handling.

Delegation

Specialized subagents receive focused prompts, tool scopes, and independent context before returning results.

Human control

Terminal status, approval, command, and issue-maintenance surfaces keep operator decisions in the loop.

Evidence surface

Public commits, tests, tool events, scheduler behavior, and issue-maintenance receipts expose runtime pressure.

Learn Through This Project

8 lessons

Compare Its Boundaries

8 labs

Latest Reporting

8 articles

Primary Sources

Open Questions

  • Can every injected context and policy result be reconstructed from the operator-facing session record?

Evidence state describes what this Atlas profile can support today. It is not a product score and it is not evidence that uninspected capabilities are absent.