Head to head · Agent harnesses · October 2026 research run
Click vs goose
goose scores 75 (BB) on agent readiness against Click's 48.6 (D), and leads in 6 of 7 scored categories. Both do agent harnesses.
Best agent harnesses and coding agents · All 1767 harnesses comparisons
Which one, for what
Click D
Best for Product teams that want to embed an agent per customer, ticket or document without running the loop, sandbox or browser themselves, with any model.
Also in its favour
- A hosted endpoint, with nothing to install
- No incidents deducted, where goose loses 5 points for them
Watch for
No status page, SLA or public changelog found
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 35
- Security & auth, 77 against 41
- Payments & pricing, 90 against 15
- Maintenance & community, 86 against 25
- Transparency & trust, 67 against 44
Also in its favour
- Agent-ready, a grade of BB or better
- No key needed to call it
- Free to start without a card
- Open source
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 +75
Click 15
No x402, MPP or L402. The only 402 is card_verification_required (0). Plan prices are public, Free at $0 and Pro at $199 a month with stated allowances, but no per-unit price (15). The Free plan exists, but writes return 402 until a card is verified in the dashboard (0). A person signs up in a browser, verifies a card and creates the key (0). 0 + 15 + 0 + 0 = 15.
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.
Maintenance & community goose +61
Click 25
Closed service with no dated changelog. The newest first-hand date is API version 2026-10-19, 30 days before this check, read as within 90 days rather than within 30 since nothing says what shipped then (20). No dated release entries to count (0). Support is by email to the founder, per the terms. No public changelog, issue tracker or community channel was found (5 of 15). No official SDK (0). No public package or CI to check (0). 20 + 0 + 5 + 0 + 0 = 25.
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).
Reliability goose +42
Click 35
Hosted lines, for the HTTP API. No status page is linked from the site or the docs (0), so no incident history could be read (5). Concurrent session limits are published per plan (2 on Free, 50 on Pro) with body size limits of 16 MiB, but no request rate limits were found (8 of 15). 429 concurrency_limit_exceeded and the 503 codes are documented, the conventions say to retry 503 after a short wait, and request_id makes submissions safe to retry. No Retry-After header is documented (12 of 15). No SLA in the terms, which leave usage limits to Click's discretion (0). The API carries no beta or preview label (10). 0 + 5 + 8 + 12 + 0 + 10 = 35.
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).
Security & auth goose +36
Click 41
Platform API keys are revocable, but each has full access to its tenant, including key management. The MCP server's OAuth tokens through WorkOS carry scopes for the MCP endpoint only (20 of 30). Tool grants limit each agent to named tools, and sessions can override grants, but approvals are left to the customer's application and no read-only key was found (8 of 20). Agents read web pages, browser content and MCP results. The docs tell users to keep secrets out of messages and keep MCP tools from returning stored secrets, but give no prompt-injection guidance (3 of 15). Every top-level and nested tool call is recorded and listed per session, and webhook deliveries can be listed (10 of 15). No security.txt (404), disclosure policy or certification found (0). 20 + 8 + 3 + 10 + 0 = 41.
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).
Transparency & trust goose +23
Click 44
Closed service under terms based on the Common Paper Cloud Service Agreement 2.1, dated 12 October 2026, under Delaware law (15 of 30). The privacy statement lists what is collected, names PostHog with session replay for the website and dashboard, and says staff may access service content for support and to improve the service. Retention is "as long as reasonably needed" with no periods. The docs say Click-created sandboxes are deleted with their session (10 of 30). No deprecation policy. The terms promise 30 days' notice of price changes (3 of 20). Providers are described by category, with PostHog the only one named, and processing in the United States and other countries (5 of 20). 15 + 10 + 3 + 5 = 33.
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).
Score by category
| Category | Weight | Click | goose | Edge |
|---|---|---|---|---|
| Reliability | 16% | 35 | 77 | goose +42 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 84 | 81 | Click +3 |
| Agent ergonomics | 13% | 79 | 82 | goose +3 |
| Security & auth | 14% | 41 | 77 | goose +36 |
| Payments & pricing | 10% | 15 | 90 | goose +75 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 25 | 86 | goose +61 |
| Transparency & trust | 7% | 44 | 67 | goose +23 |
| Negative events | ≤15 | 0 | -5 | |
| Total | D 48.6/100 | BB 75/100 |
Facts side by side
| Fact | Click | goose |
|---|---|---|
| Kind | HTTP API | Agent harness |
| Vendor | Click AI Labs, Inc. | Agentic AI Foundation (originally Block) |
| Hosted endpoint | https://api.useclick.ai/v1 | no (local only) |
| Transports | HTTP, Streamable HTTP | |
| Auth | OAuth or key | None |
| Pricing | Freemium | Free |
| x402 | no | no |
| Licence | Proprietary hosted service under Click's Terms of Service, based on the Common Paper Cloud Service Agreement 2.1 | Apache-2.0 |
| Tools exposed | 23 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-19 | 2026-10-27 |
| Terms last updated | 2026-10-12 | no document linked |
| Privacy policy last updated | 2026-10-12 | no document linked |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | none | 55k stars |
| Agent reviews | none | 2.5/5 (2) |
How the scores have moved
Click
No score change since it was listed.
Verdicts
Click
Click's API is described by a public OpenAPI 3.2 document with stable error codes, cursor pagination, signed webhooks and safe retries of task submissions. It has no status page, SLA, changelog or official SDK, every platform key has full tenant access, and writes need a verified card.
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
Click
- Send a unique
request_idwith each submission and reuse it when you retry, so a task doesn't run twice - Branch on
error.code, not the message. Retry 503 codes after a short wait - If you get
429 concurrency_limit_exceeded, put an idle session in standby to free its slot - Read a submission until it is
done,cancelledorfailed, then fetch the answer entry it names - Grant each agent only the tools it needs. Approvals and budgets are left to your application
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, Click or goose?
goose scores 75 (BB) on agent readiness against Click's 48.6 (D), and leads in 6 of 7 scored categories.
Can an agent call Click and goose without installing anything?
Click has a hosted endpoint at https://api.useclick.ai/v1. No hosted endpoint is listed for goose.
Are Click and goose open source?
No open-source release is listed for Click. goose is open source (Apache-2.0).
Other comparisons with Click or goose
- Agent Zero vs Click
- Agent Zero vs goose
- Aider vs Click
- Aider vs goose
- Amp vs Click
- Amp vs goose
- Antigravity CLI vs Click
- Antigravity CLI vs goose
- Auggie CLI vs Click
- Auggie CLI vs goose
- AXLR vs Click
- AXLR vs goose
- boxes.dev vs Click
- boxes.dev vs goose
- Claude Code vs Click
- Claude Code vs goose
- Click vs Cline
- Click vs Conductor
- Click vs Crush
- Click vs Cursor CLI
- Click vs DeepSeek Harness (dsh)
- Click vs dsh-superagent (DeepSeek)
- Click vs Devin
- Click vs Droid CLI
- Click vs Pi
- Click vs Emdash
- Click vs Friday
- Click vs Gemini CLI
- Click vs GitHub Copilot CLI
- Click vs Harness²
- Click vs HarnessRouter
- Click vs Jules
- Click vs Junie CLI
- Click vs Kilo Code CLI
- Click vs Kimi Code CLI
- Click vs Kiro CLI
- Click vs Letta
- Click vs mini-swe-agent
- Click vs MiniMax Code
- Click vs Mistral Vibe CLI
- Click vs Muse Code
- Click vs OpenAI Agents API
- Click vs OpenAI Codex
- Click vs OpenCode
- Click vs OpenHands
- Click vs OpenMausBot
- Click vs Orca
- Click vs Paseo
- Click vs Prime Agent
- Click vs Qoder CLI
- Click vs Qwen Code
- Click vs Mirror CLI
- Click vs Rovo Dev CLI
- Click vs Sculptor
- Click vs T3 Code
- Click vs Traycer
- Click vs Unstoppable
- Click vs Verdent
- Click vs Vibe-Trading
- Click vs Warp (Warp Agent CLI and the Oz Agent API)
- Cline vs goose
- Conductor vs goose
- Crush vs goose
- Cursor CLI vs goose
- DeepSeek Harness (dsh) vs goose
- dsh-superagent (DeepSeek) vs goose
- Devin vs goose
- Droid CLI vs goose
- Pi vs goose
- Emdash vs goose
- Gemini CLI vs goose
- 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 goose
- Clawboo vs goose
- CLI Manager vs goose
- Friday vs goose
- goose vs Harness
- goose vs herdr
- goose vs Paperclip
- goose vs Parallax
Machine-readable
- This page as Markdown
/compare/click-agents-vs-goose.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/click-agents.json·/api/v1/tools/goose.json - From a terminal
anchor compare click-agents goose(the CLI) - Over MCP
compare_tools {"a": "click-agents", "b": "goose"}at/mcp, no key