Gemini CLI vs mini-swe-agent

Gemini CLI

Apache-2.0, with 16 stable releases since 3 July and documented headless output. Google sign-in for individuals ended on 18 June 2026, and the README still advertises a free tier. Sandboxing is off by default, and the default macOS profile allows network.

mini-swe-agent

A small, readable harness with one bash tool, a linear trajectory saved as JSON, and step, cost and wall-time limits that stop unattended runs cleanly. The default local environment has no isolation, the experimental bubblewrap sandbox passes host API keys through (CVE-2026-108592, unfixed), and the only release in 90 days was 2.4.6 on 23 July 2026.

Gemini CLI

1. Set GEMINI_TRUST_WORKSPACE to true only for trusted inputs in CI. Since 0.39.1 headless mode doesn't trust a folder on its own
2. Turn on the sandbox with -s or tools.sandbox, and pick a proxied Seatbelt profile on macOS to cut network
3. Set privacy.usageStatisticsEnabled to false to stop usage statistics
4. Since 0.63.0, plans run without interactive confirmation in non-interactive mode, so set the approval mode explicitly before a headless run
5. Authenticate with a paid Gemini API key or Vertex credentials. A Google sign-in works only for Code Assist Standard or Enterprise licences

mini-swe-agent

1. Run with -y --exit-immediately for unattended use. Without --exit-immediately it waits for input when the agent finishes
2. Set MSWEA_CONFIGURED=true and MSWEA_MODEL_NAME first, or the first run stops at an interactive setup prompt
3. Read info.exit_status in the -o trajectory file. A run that hits its limits still exits normally
4. For untrusted repositories use -c mini.yaml -c environment.environment_class=docker -c environment.image=<image>. The local and bubblewrap environments both expose host variables
5. Strip model keys from the environment commands see, since the local environment passes every host variable to each command