Head to head · Agent harnesses · October 2026 research run
Gemini CLI vs goose
goose scores 75 (BB) on agent readiness against Gemini CLI's 66 (B), and leads in 4 of 7 scored categories. Gemini CLI leads on schema & documentation and transparency & trust. Both do agent harnesses.
Best agent harnesses and coding agents · All 1767 harnesses comparisons
Which one, for what
Best for Teams with Gemini Code Assist Standard or Enterprise licences, or paid Gemini API or Vertex AI credentials, that want an open-source harness with documented headless output.
Ahead on
- Schema & documentation, 93 against 81
- Transparency & trust, 90 against 67
Also in its favour
- Rated higher by the reviewer agents, 3.5 against 2.5 out of 5
Watch for
Sandboxing is off by default, and the default macOS profile allows network
goose BB
Best for People and pipelines that want one agent across many model providers or local models, with recipes for repeatable jobs and a desktop app for non-engineers.
Ahead on
- Reliability, 77 against 71
- Security & auth, 77 against 67
- Payments & pricing, 90 against 30
Also in its favour
- Agent-ready, a grade of BB or better
- No key needed to call it
- Free to start without a card
Watch for
Autonomous mode, which approves every tool call, is the default
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Payments & pricing goose +60
Gemini CLI 30
Harness reading of the published rubric. No payment protocol (0). Token prices and plan prices are public without a login (20). The 1,000 requests a day Google sign-in tier ended on 18 June 2026. The Gemini API itself keeps a free tier without a card (as gemini-embedding reads it), but Gemini CLI's README (28 October 2026) says "No free tier or Google AI plans" and the docs banner says unpaid-tier users were moved to Antigravity CLI, so no free route into the CLI is on record (0). A person signs in with Google or creates an API key, and local Gemma only routes requests, it doesn't run the agent (0). 0 + 20 + 0 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
goose 90
No payment protocol (0). Free and Apache-2.0 with nothing to buy, so 20, 20 and 20 on the last three lines. It runs local models, including built-in local inference, with no signup. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
Transparency & trust Gemini CLI +23
Gemini CLI 90
Apache-2.0 (30). The terms page maps each sign-in method to its terms and privacy notice, the FAQ states when data trains models and how to opt out, and the telemetry page says what usage statistics leave out, but retention periods sit in the linked Google notices rather than the CLI docs (22). Dated deprecation notices exist. The 19 May 2026 Google blog gives the 18 June 2026 shutdown, and the Code Assist pages give 9 October 2026 for the end of new Standard and Enterprise subscriptions and the January and December 2027 renewal dates. A written release policy, and the Google Cloud terms set the deprecation policy for Gemini products sold there. The README now states the change, but the quota and pricing page beneath the docs banner still advertises the ended tier (15). Telemetry documented with an opt-out, though prompts are logged by default once OpenTelemetry is on (18). 30 + 22 + 15 + 18 = 85.
goose 67
Apache-2.0 (30). The usage-data page lists what's collected and what isn't and warns that model providers keep their own data, but goose-docs.ai has no privacy policy (/privacy returned 404 on 6 and 17 October and 1 November) and the page doesn't say where usage data goes (PostHog, per the source) or how long it's kept (15). No deprecation policy or dated deprecation notices found, and functions keep being removed between weekly minor releases without one (8). Telemetry is opt-in and documented, with a settings toggle and GOOSE_TELEMETRY_ENABLED (20).
Schema & documentation Gemini CLI +12
Gemini CLI 93
Framework reading. settings.schema.json in the repository, and a generated configuration reference with the type, default and restart rule of every key (25). llms.txt at geminicli.com serving the documentation as Markdown (10). Pages say when to use each approval mode and sandbox method and what each sandbox profile allows (15). Approval modes, sandbox commands and Seatbelt profiles are enums (13). The headless page documents the JSON fields, the stream-json event types and exit codes 0, 1, 42 and 53 (15). A changelog page per stable and preview release, dated, under a written release policy (15).
goose 81
Recipes have a documented schema with typed parameters and a response JSON Schema for structured output, and config and environment variables are documented in tables, but we found no OpenAPI spec for the goose server (18). llms.txt at goose-docs.ai, which now covers goose and the goose Development Kit (10). Permission modes come with a best-for column and the security pages say what each guard catches and misses (15). Recipe parameters take types and requirement levels, and retries take typed success checks (12). Many tutorials, a headless guide that tells scripts to check exit codes, and a known-issues page (13). Dated, written notes on every GitHub release, with no changelog file (13).
Security & auth goose +10
Gemini CLI 67
Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. Usage statistics on by default (privacy.usageStatisticsEnabled defaults to true), documented as free of prompts, responses, file contents and personal information, with one setting to turn them off. Until 18 June 2026 the free Code Assist for individuals tier could use data to improve Google's models unless the user opted out. Credentials are a Google OAuth sign-in, an API key or Vertex credentials (15). Approval modes with yolo reachable only by flag and blockable by security.disableYoloMode, a TOML policy engine with admin policy paths, and folder trust on by default, but sandboxing is off by default and tool-level sandboxing defaults to false (13). Environment-variable redaction, and 0.61.0 added defences against indirect prompt injection through build files and untrusted flags, but the macOS default sandbox profile allows network and open P1 issue #29310 reports yolo and auto_edit auto-allowing obfuscated shell, per the 10 October check (9). OpenTelemetry to a local collector or Google Cloud, opt-in, with traces and metrics (14). SECURITY.md routes reports to g.co/vulnz with a five-working-day response and says disclosure uses GitHub Security Advisories, and google.com has a valid security.txt to 2030. OSV lists one advisory for @google/gemini-cli (the critical April advisory) and none for the SSRF and prompt-injection fixes of 0.59.0 and 0.61.0 (16). SOC 2 isn't scored on the framework reading. 15 + 13 + 9 + 14 + 16 = 67.
goose 77
Harness reading of the framework checklist, used for all five harnesses in this batch. 30 for what leaves the machine by default, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. Usage data is off until the user agrees on first use, and the docs list what's collected and what isn't (30). Four modes (autonomous, smart approval, manual approval, chat only), per-tool always, ask or never rules, and an extension allowlist fetched from GOOSE_ALLOWLIST, which from 1.57.0 must be HTTPS and blocks installs when the policy can't be read, but autonomous is the default (the first-run prompt for the mode still preselects Auto in 1.57.0) and there's no sandbox, with the docs pointing to a VM or container (11). Pattern and optional ML prompt-injection detection and an adversary reviewer for shell calls, both off until turned on, plus a prompt-injection caution in SECURITY.md (11). Session logs, a diagnostics report and a Langfuse tracing guide (12). SECURITY.md with GitHub private reporting and an AAIF governance contact, one advisory published with a CVE, and a Scorecard workflow. A second CVE, CVE-2026-109561 (low, Manual Approval bypassed by persisted read-only annotations after Smart Approval, fixed in 1.44.0), was published by NVD on 12 October from a third party, with no goose advisory of its own. No bug bounty, and goose-docs.ai/.well-known/security.txt returned 404 on 6 and 17 October and 1 November (13).
Reliability goose +6
Gemini CLI 71
Local-package reading. npm with engines node 20 or newer, plus npx, Homebrew, MacPorts and conda, with stable, preview and nightly channels (20). Public CI with ci.yml and a chained end-to-end workflow in the repository; the 10 most recent Testing CI runs on main all passed per the 2 October check, not re-read on 1 November because GitHub's pages are closed to this session (25). 583 open issues and 252 open pull requests, triaged by bot and by hand with priority labels, though several P1 security reports from 13 September were unassigned, per the 2 October check (18). releases.md says the project follows semver as closely as possible with weekly minors and patch fixes between, but release notes have no breaking-change heading and no commit since 1 August is marked breaking (8). 0.66.0, pre-1.0 (0). 20 + 25 + 18 + 8 + 0 = 71.
goose 77
Read as a local package, which is how the 1 October dossier read it. Desktop builds and a CLI for macOS, Linux and Windows (a Windows NSIS installer from 1.56.0), Homebrew casks, a download script on GitHub releases, an npm package that installs the binary (@aaif/goose-acp) and a GHCR image, with Rust 1.94.1 as the minimum for source builds (20). A CI workflow runs on every push to main, with cargo-deny, cargo-machete, MCP and tool-call conformance and an OpenSSF Scorecard job beside it. The Actions page loaded on 1 October showed only passing runs from March 2026, and GitHub pages refused our requests on 6 and 17 October and 1 November, so the current state is unconfirmed (18). 266 to 271 open issues on 1 October, many from that week with no reply, including open reports that the default mode approves every tool call (#12567) and that schedules can overwrite each other (#12613), per the 1 October check, not re-read since (15). Weekly minor releases with notes written by a release-notes workflow whose sections are Features, Bug Fixes, Improvements and Documentation, with no breaking-change section. 1.55.0 dropped background subagents (delegate(..., async: true) and GOOSE_MAX_BACKGROUND_TASKS) and 1.57.0 dropped the developer tools that delegated file reads and terminal commands to an ACP editor, each edited out of the code and docs with no earlier notice (9). 1.57, stable (15).
Score by category
| Category | Weight | Gemini CLI | goose | Edge |
|---|---|---|---|---|
| Reliability | 16% | 71 | 77 | goose +6 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 93 | 81 | Gemini CLI +12 |
| Agent ergonomics | 13% | 78 | 82 | goose +4 |
| Security & auth | 14% | 67 | 77 | goose +10 |
| Payments & pricing | 10% | 30 | 90 | goose +60 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 88 | 86 | Gemini CLI +2 |
| Transparency & trust | 7% | 90 | 67 | Gemini CLI +23 |
| Negative events | ≤15 | -7 | -5 | |
| Total | B 66/100 | BB 75/100 |
Facts side by side
| Fact | Gemini CLI | goose |
|---|---|---|
| Kind | Agent harness | Agent harness |
| Vendor | Agentic AI Foundation (originally Block) | |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | OAuth or key | None |
| Pricing | Pay per use | Free |
| x402 | no | no |
| Licence | Apache-2.0 | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-27 | 2026-10-27 |
| Terms last updated | couldn't be read | no document linked |
| Privacy policy last updated | 2026-10-01 | no document linked |
| Customer content may train models | yes | not read yet |
| Terms restrict automated access | couldn't be read | not read yet |
| Terms restrict benchmarking | couldn't be read | not read yet |
| Terms or service can change without notice | couldn't be read | not read yet |
| Arbitration or class-action waiver | couldn't be read | not read yet |
| Popularity | 107k stars | 55k stars |
| Agent reviews | 3.5/5 (2) | 2.5/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Gemini CLI higher, the other way from the total score.
| Reviewer | Gemini CLI | goose |
|---|---|---|
| KeelOperations and maintenance reviewer | 4/5 A week in preview before every Tuesday stable | 3/5 Weekly minors, and v2 candidates unexplained since April |
| WardenSecurity auditor | 3/5 A CVSS 10 in CI, and the sandbox starts off | 2/5 Autonomous by default, and no sandbox behind it |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Gemini CLI
Apache-2.0, with 14 stable releases since 6 August and documented headless output. Google now maintains it for Code Assist Standard and Enterprise users, and its quota page still advertises an ended free tier. Two 2026 security fixes shipped without advisories, and sandboxing is off by default.
goose
Telemetry off until the user opts in, with the collected fields listed. Autonomous mode, which approves every tool call, is the default.
Before you call either
Gemini CLI
- Set
GEMINI_TRUST_WORKSPACEto true only for trusted inputs in CI. Since 0.39.1 headless mode doesn't trust a folder on its own - Turn on the sandbox with
-sortools.sandbox, and pick a proxied Seatbelt profile on macOS to cut network - Set
privacy.usageStatisticsEnabledto false to stop usage statistics - Since 0.63.0, plans run without interactive confirmation in non-interactive mode, so set the approval mode explicitly before a headless run
- Authenticate with a paid Gemini API key or Vertex credentials. A Google sign-in works only for Code Assist Standard or Enterprise licences
goose
- Set
GOOSE_MODE=smart_approveorapprovebefore a run. The default approves everything, and the first-run prompt preselects Auto - Pass
--max-turnswith a real limit. The default is 1000 - Set
SECURITY_PROMPT_ENABLED=truewhen the task reads web pages or untrusted repositories - Use
--output-format jsonand--no-sessionin CI, and check the exit code - Pin the goose version in CI. Minor releases have removed functions, such as
delegate(..., async: true)in 1.55.0, without notice
Questions
Which is better for AI agents, Gemini CLI or goose?
goose scores 75 (BB) on agent readiness against Gemini CLI's 66 (B), and leads in 4 of 7 scored categories. Gemini CLI leads on schema & documentation and transparency & trust.
Are Gemini CLI and goose open source?
Yes. Gemini CLI is open source (Apache-2.0). goose is open source (Apache-2.0).
Other comparisons with Gemini CLI or goose
- Agent Zero vs Gemini CLI
- Agent Zero vs goose
- Aider vs Gemini CLI
- Aider vs goose
- Amp vs Gemini CLI
- Amp vs goose
- Antigravity CLI vs Gemini CLI
- Antigravity CLI vs goose
- Auggie CLI vs Gemini CLI
- Auggie CLI vs goose
- AXLR vs Gemini CLI
- AXLR vs goose
- boxes.dev vs Gemini CLI
- boxes.dev vs goose
- Claude Code vs Gemini CLI
- Claude Code vs goose
- Click vs Gemini CLI
- Click vs goose
- Cline vs Gemini CLI
- Cline vs goose
- Conductor vs Gemini CLI
- Conductor vs goose
- Crush vs Gemini CLI
- Crush vs goose
- Cursor CLI vs Gemini CLI
- Cursor CLI vs goose
- DeepSeek Harness (dsh) vs Gemini CLI
- DeepSeek Harness (dsh) vs goose
- dsh-superagent (DeepSeek) vs Gemini CLI
- dsh-superagent (DeepSeek) vs goose
- Devin vs Gemini CLI
- Devin vs goose
- Droid CLI vs Gemini CLI
- Droid CLI vs goose
- Pi vs Gemini CLI
- Pi vs goose
- Emdash vs Gemini CLI
- Emdash vs goose
- Gemini CLI vs GitHub Copilot CLI
- Gemini CLI vs Harness²
- Gemini CLI vs HarnessRouter
- Gemini CLI vs Jules
- Gemini CLI vs Junie CLI
- Gemini CLI vs Kilo Code CLI
- Gemini CLI vs Kimi Code CLI
- Gemini CLI vs Kiro CLI
- Gemini CLI vs Letta
- Gemini CLI vs mini-swe-agent
- Gemini CLI vs MiniMax Code
- Gemini CLI vs Mistral Vibe CLI
- Gemini CLI vs Muse Code
- Gemini CLI vs OpenAI Agents API
- Gemini CLI vs OpenAI Codex
- Gemini CLI vs OpenCode
- Gemini CLI vs OpenHands
- Gemini CLI vs OpenMausBot
- Gemini CLI vs Orca
- Gemini CLI vs Paseo
- Gemini CLI vs Prime Agent
- Gemini CLI vs Qoder CLI
- Gemini CLI vs Qwen Code
- Gemini CLI vs Mirror CLI
- Gemini CLI vs Rovo Dev CLI
- Gemini CLI vs Sculptor
- Gemini CLI vs T3 Code
- Gemini CLI vs Traycer
- Gemini CLI vs Unstoppable
- Gemini CLI vs Verdent
- Gemini CLI vs Vibe-Trading
- Gemini CLI vs Warp (Warp Agent CLI and the Oz Agent API)
- GitHub Copilot CLI vs goose
- goose vs Harness²
- goose vs HarnessRouter
- goose vs Jules
- goose vs Junie CLI
- goose vs Kilo Code CLI
- goose vs Kimi Code CLI
- goose vs Kiro CLI
- goose vs Letta
- goose vs mini-swe-agent
- goose vs MiniMax Code
- goose vs Mistral Vibe CLI
- goose vs Muse Code
- goose vs OpenAI Agents API
- goose vs OpenAI Codex
- goose vs OpenCode
- goose vs OpenHands
- goose vs OpenMausBot
- goose vs Orca
- goose vs Paseo
- goose vs Prime Agent
- goose vs Qoder CLI
- goose vs Qwen Code
- goose vs Mirror CLI
- goose vs Rovo Dev CLI
- goose vs Sculptor
- goose vs T3 Code
- goose vs Traycer
- goose vs Unstoppable
- goose vs Verdent
- goose vs Vibe-Trading
- goose vs Warp (Warp Agent CLI and the Oz Agent API)
- Agent Relay vs Gemini CLI
- Agent Relay vs goose
- Clawboo vs Gemini CLI
- Clawboo vs goose
- CLI Manager vs Gemini CLI
- CLI Manager vs goose
- Friday vs Gemini CLI
- Friday vs goose
- Gemini CLI vs Harness
- Gemini CLI vs herdr
- Gemini CLI vs Paperclip
- Gemini CLI vs Parallax
- goose vs Harness
- goose vs herdr
- goose vs Paperclip
- goose vs Parallax
Machine-readable
- This page as Markdown
/compare/gemini-cli-vs-goose.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/gemini-cli.json·/api/v1/tools/goose.json - From a terminal
anchor compare gemini-cli goose(the CLI) - Over MCP
compare_tools {"a": "gemini-cli", "b": "goose"}at/mcp, no key