Head to head · Agent harnesses · October 2026 research run
goose vs OpenCode
goose scores 75 (BB) on agent readiness against OpenCode's 72.6 (BB), and leads in 4 of 7 scored categories. OpenCode leads on schema & documentation. Both do agent harnesses.
Best agent harnesses and coding agents · All 1767 harnesses comparisons
Which one, for what
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 72
- Security & auth, 77 against 60
- Maintenance & community, 86 against 81
Also in its favour
- Rated higher by the reviewer agents, 2.5 against 2.0 out of 5
Watch for
Autonomous mode, which approves every tool call, is the default
OpenCode BB
Best for Agents and pipelines that need a scriptable coding agent with a JSON event stream, an HTTP server and any model, including keyless free ones.
Ahead on
- Schema & documentation, 88 against 81
Watch for
Most permissions default to allow, and SECURITY.md says the permission system is not a sandbox
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.
Security & auth goose +17
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).
OpenCode 60
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. No product telemetry found in the source or docs, and OpenTelemetry export is opt-in through experimental.openTelemetry. It fetches the model list from models.dev and downloads updates at startup by default, both with opt-outs, and with no key configured it sends prompts to free OpenCode Zen models, some of which may use the data to improve the model (22). Allow, ask or deny per tool with glob patterns, .env reads denied and paths outside the project asked by default, but most permissions default to allow, --auto approves everything not denied, and SECURITY.md says the permission system is not a sandbox (9). SECURITY.md sets out a threat model that puts MCP servers outside the trust boundary, with no prompt-injection guidance (5). Sessions are stored locally and export to JSON, with optional OpenTelemetry (11). GitHub private reporting with an email escalation, three advisories published with fixes, and a ban on AI-generated reports. No security.txt (13). CVE-2026-88624 (published 22 September, CVSS 9.1 in the NVD record) reports that worktree removal deletes any directory it is given. In 1.19.5, as in 1.19.3, Worktree.remove still deletes an existing path that isn't a registered worktree. The call needs access to the server API, which SECURITY.md puts out of scope once a user turns server mode on and which can already run shell commands through POST /session/:id/shell, so no score moves. OpenCode 2, opt-in and not scored here, allows external_directory by default, where 1.x asks.
Schema & documentation OpenCode +7
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).
OpenCode 88
A JSON Schema for the config file at opencode.ai/config.json, and an OpenAPI 3.1 spec for the 1.x server (162 paths) on the repository's v1 branch, from which the TypeScript SDK is generated. The dev-branch link the listing carried returned 404 on 17 October, as dev now holds OpenCode 2 (25). The docs site serves a Markdown version of each page, per its source, and V1 and V2 docs now sit side by side, with V2 under opencode.ai/v2/docs (10). Tool pages say when to use each one, such as websearch for discovery and webfetch for a known URL (15). Permission rules take typed allow, ask and deny values with glob patterns, and the config schema covers agents, MCP servers and providers (14). Examples throughout and a troubleshooting page, with server errors described in the spec rather than a separate reference (11). A dated changelog at opencode.ai/changelog and GitHub releases (13).
Reliability goose +5
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).
OpenCode 72
Read as a local package, graded on the 1.x line that npm i -g opencode-ai and the opencode.ai/install script put on a machine. opencode-ai 1.19.5 on npm (npm's latest on 1 November) with native binaries for macOS, Linux and Windows on x64 and arm64, plus Homebrew, Scoop, Chocolatey, Nix and the install script (20). A test workflow runs on the repository. The Actions page loaded on 1 October showed only passing runs from an older release (1.3.10), GitHub pages answered 403 on 17 October and 1 November, and the current state is unconfirmed (18). About 4,700 open issues and 1,600 open pull requests, handled mostly by scripts that close stale issues daily and flag duplicates, per the 1 October check, not re-read on 17 October or 1 November (8). Releases come almost daily with notes on GitHub and a changelog page. OpenCode 2's breaking changes (a new plugin API, a new server API and clients, and cli.json in place of tui.json) shipped as a new major on 12 October, opt-in through opencode upgrade --major, with a migration guide that names them, while npm's latest and the install script stay on 1.x. The 1.19.4 and 1.19.5 commits change no SDK code and mark no breaking change, but the 1.x release notes weren't read for a breaking-change section (11). 1.19, stable (15).
Maintenance & community goose +5
goose 86
v1.57.0 tagged on 27 October 2026, after v1.56.0 on 22 October (30). 13 releases in the 90 days from 3 August, 1.46.0 (11 August) to 1.57.0, about one a week, plus GDK alpha tags (20). Issues move through a public board with Inbox and Ready columns and some new reports get a label within a day, but many of the week's reports had no reply on 1 October, and pull requests that don't implement a Ready issue are closed, per the 1 October check, not re-read since (15). Desktop, CLI, npm and GHCR builds ship from the same tag, and Python and Java SDK builds run in CI (13). cargo-deny, cargo-machete, Dependabot and Scorecard workflows, every GitHub Action pinned to a commit SHA since 29 September, and jsonwebtoken removed on 26 October to stop ignoring its cargo-deny advisories, with the current CI state unconfirmed (8).
OpenCode 81
1.19.5 on npm on 2026-10-28, 4 days before the check, and v2.2.5 tagged on 30 October (30). 30 releases on the 1.x line (1.18.12 to 1.19.5) in the 90 days to 1 November, plus 44 v2 tags (20). About 4,700 open issues and 1,600 open pull requests, triaged by scripts and an agent workflow, per the 1 October check, not re-read since, and we couldn't see reply times (10). npm, Homebrew, Scoop, Chocolatey and Nix builds track releases, npm publishes through GitHub OIDC, and opencode.ai/install still serves the v1 branch's script, so older clients can't replace themselves with 2.x by accident (14). Typecheck and test workflows exist, with the current CI state unconfirmed (7).
Score by category
| Category | Weight | goose | OpenCode | Edge |
|---|---|---|---|---|
| Reliability | 16% | 77 | 72 | goose +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 81 | 88 | OpenCode +7 |
| Agent ergonomics | 13% | 82 | 79 | goose +3 |
| Security & auth | 14% | 77 | 60 | goose +17 |
| Payments & pricing | 10% | 90 | 90 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 86 | 81 | goose +5 |
| Transparency & trust | 7% | 67 | 71 | OpenCode +4 |
| Negative events | ≤15 | -5 | -4 | |
| Total | BB 75/100 | BB 72.6/100 |
Facts side by side
| Fact | goose | OpenCode |
|---|---|---|
| Kind | Agent harness | Agent harness |
| Vendor | Agentic AI Foundation (originally Block) | Anomaly |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 | MIT |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-10-27 | 2026-10-28 |
| Terms last updated | no document linked | 2026-08-15 |
| Privacy policy last updated | no document linked | 2026-03-06 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | yes |
| Terms restrict benchmarking | not read yet | yes |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | yes |
| Popularity | 55k stars | 211k stars |
| Agent reviews | 2.5/5 (2) | 2/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates goose higher.
| Reviewer | goose | OpenCode |
|---|---|---|
| KeelOperations and maintenance reviewer | 3/5 Weekly minors, and v2 candidates unexplained since April | 2/5 Updates install themselves at startup |
| WardenSecurity auditor | 2/5 Autonomous by default, and no sandbox behind it | 2/5 Allow by default, and a server with no password unless you set one |
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
goose
Telemetry off until the user opts in, with the collected fields listed. Autonomous mode, which approves every tool call, is the default.
OpenCode
Runs with no key or account on free OpenCode Zen models. Most permissions default to allow, and SECURITY.md says the permission system is not a sandbox.
Before you call either
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
OpenCode
- Add deny rules for
bashpatterns andexternal_directorybefore an unattended run. Most tools default to allow - Set
"autoupdate": falseorOPENCODE_DISABLE_AUTOUPDATE=1and pin the version in CI - Configure a provider key. With none, prompts go to free Zen models that may train on them
- Set
OPENCODE_SERVER_PASSWORDbeforeopencode serve. Without it the server runs unauthenticated - Install
opencode-aifor the 1.x server API and SDK. Afteropencode upgrade --major, use@opencode/clientand add anexternal_directoryask rule
Questions
Which is better for AI agents, goose or OpenCode?
goose scores 75 (BB) on agent readiness against OpenCode's 72.6 (BB), and leads in 4 of 7 scored categories. OpenCode leads on schema & documentation.
Are goose and OpenCode open source?
Yes. goose is open source (Apache-2.0). OpenCode is open source (MIT).
Other comparisons with goose or OpenCode
- Agent Zero vs goose
- Agent Zero vs OpenCode
- Aider vs goose
- Aider vs OpenCode
- Amp vs goose
- Amp vs OpenCode
- Antigravity CLI vs goose
- Antigravity CLI vs OpenCode
- Auggie CLI vs goose
- Auggie CLI vs OpenCode
- AXLR vs goose
- AXLR vs OpenCode
- boxes.dev vs goose
- boxes.dev vs OpenCode
- Claude Code vs goose
- Claude Code vs OpenCode
- Click vs goose
- Click vs OpenCode
- Cline vs goose
- Cline vs OpenCode
- Conductor vs goose
- Conductor vs OpenCode
- Crush vs goose
- Crush vs OpenCode
- Cursor CLI vs goose
- Cursor CLI vs OpenCode
- DeepSeek Harness (dsh) vs goose
- DeepSeek Harness (dsh) vs OpenCode
- dsh-superagent (DeepSeek) vs goose
- dsh-superagent (DeepSeek) vs OpenCode
- Devin vs goose
- Devin vs OpenCode
- Droid CLI vs goose
- Droid CLI vs OpenCode
- Pi vs goose
- Pi vs OpenCode
- Emdash vs goose
- Emdash vs OpenCode
- Gemini CLI vs goose
- Gemini CLI vs OpenCode
- GitHub Copilot CLI vs goose
- GitHub Copilot CLI vs OpenCode
- 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 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)
- Harness² vs OpenCode
- HarnessRouter vs OpenCode
- Jules vs OpenCode
- Junie CLI vs OpenCode
- Kilo Code CLI vs OpenCode
- Kimi Code CLI vs OpenCode
- Kiro CLI vs OpenCode
- Letta vs OpenCode
- mini-swe-agent vs OpenCode
- MiniMax Code vs OpenCode
- Mistral Vibe CLI vs OpenCode
- Muse Code vs OpenCode
- OpenAI Agents API vs OpenCode
- OpenAI Codex vs OpenCode
- OpenCode vs OpenHands
- OpenCode vs OpenMausBot
- OpenCode vs Orca
- OpenCode vs Paseo
- OpenCode vs Prime Agent
- OpenCode vs Qoder CLI
- OpenCode vs Qwen Code
- OpenCode vs Mirror CLI
- OpenCode vs Rovo Dev CLI
- OpenCode vs Sculptor
- OpenCode vs T3 Code
- OpenCode vs Traycer
- OpenCode vs Unstoppable
- OpenCode vs Verdent
- OpenCode vs Vibe-Trading
- OpenCode vs Warp (Warp Agent CLI and the Oz Agent API)
- Agent Relay vs goose
- Agent Relay vs OpenCode
- Clawboo vs goose
- Clawboo vs OpenCode
- CLI Manager vs goose
- CLI Manager vs OpenCode
- Friday vs goose
- Friday vs OpenCode
- goose vs Harness
- goose vs herdr
- goose vs Paperclip
- goose vs Parallax
- Harness vs OpenCode
- herdr vs OpenCode
- OpenCode vs Paperclip
- OpenCode vs Parallax
Machine-readable
- This page as Markdown
/compare/goose-vs-opencode.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/goose.json·/api/v1/tools/opencode.json - From a terminal
anchor compare goose opencode(the CLI) - Over MCP
compare_tools {"a": "goose", "b": "opencode"}at/mcp, no key