The outcome

Create a verified change that can be inspected or restored without exposing unnecessary system authority.

Gemini CLI is a open-source Gemini-powered terminal agent for software development and automation. Completing bounded repository tasks from the terminal with explicit tool approvals, optional sandboxing, recoverable checkpoints, and scriptable output. This guide narrows that broad capability into one repeatable outcome, with checkpoints that keep the source material and your judgment in the loop.

Before you begin

Set the boundary before the tool starts.

Choose one real task, identify who will use the result, and decide what evidence or test will make the result acceptable. Gather only the source material needed for that task. If the work contains confidential, personal, regulated, or client-owned information, confirm that the platform and account are approved before sharing it.

Troiana principle

AI should make the work easier to inspect. If the workflow removes the source, the owner, or the review step, redesign the workflow.

Step by step

A workflow you can repeat.

  1. 01

    Create a clean branch, review repository instructions and extensions, confirm folder trust, and capture status and baseline tests.

  2. 02

    Enable checkpointing and an appropriate sandbox, verify permitted filesystem and network access, and keep YOLO mode disabled.

  3. 03

    Provide the outcome, acceptance criteria, relevant files, architecture constraints, non-goals, validation commands, and protected resources.

  4. 04

    Review each shell command, file edit, extension or MCP call, network request, dependency change, and sandbox expansion before allowing it.

  5. 05

    Run trusted checks independently, inspect the complete diff and saved checkpoint, and commit or release only through the repository's normal review process.

Working standard

What good use looks like.

  • Enable recovery before edits.
  • Keep YOLO mode off.
  • Review sandbox expansion requests.

Gemini CLI can invoke tools automatically, execute shell commands, modify files, use extensions and MCP servers, and access network services when permitted. Sandboxing and checkpointing are not universal guarantees and may require explicit setup; YOLO mode auto-approves actions. Keep high-risk work in a disposable environment, review trust and extension code, restrict credentials and network access, avoid unattended side effects, and verify restored checkpoints and final results.

Official references

Check the current product documentation.

Features, plan limits, availability, and data controls change. These official pages are the starting points used for this collection.