Head to head · Agent harness · October 2026 research run
goose vs Kilo Code CLI
Kilo Code CLI scores 75.4 (BB) on agent readiness against goose's 73.9 (BB), and leads in 4 of 7 scored categories. goose leads on agent ergonomics, security & auth and payments & pricing. Both do agent harness.
Which one, for what
goose BB
Good 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
- Agent ergonomics, 82 against 72
- Security & auth, 77 against 66
- Payments & pricing, 60 against 50
Also in its favour
- No key needed to call it
Watch for
Autonomous mode, which approves every tool call, is the default
Good for Developers who want an open-source terminal agent with per-tool permission rules, an optional sandbox and a choice of provider, and the same engine in VS Code and JetBrains.
Ahead on
- Reliability, 85 against 77
- Schema & documentation, 90 against 81
- Transparency & trust, 76 against 63
Watch for
Telemetry to PostHog is on by default, and the privacy policy and PRIVACY.md don't mention it
Score by category
| Category | Weight this run | goose | Kilo Code CLI | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 77 | 85 | Kilo Code CLI +8 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 81 | 90 | Kilo Code CLI +9 |
| Agent ergonomics | 13%16.2 | 82 | 72 | goose +10 |
| Security & auth | 14%17.5 | 77 | 66 | goose +11 |
| Payments & pricing | 10%12.5 | 60 | 50 | goose +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 86 | 87 | Kilo Code CLI +1 |
| Transparency & trust | 7%8.8 | 63 | 76 | Kilo Code CLI +13 |
| Negative events | ≤15 | -2 | 0 | |
| Total | 73.9 · BB | 75.4 · BB |
Facts side by side
| Fact | goose | Kilo Code CLI |
|---|---|---|
| Kind | Agent harness | Agent harness |
| Vendor | Agentic AI Foundation (originally Block) | Kilo Code Inc. |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 | MIT |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-23 | 2026-10-07 |
| Terms last updated | no document linked | 2026-09-30 |
| Privacy policy last updated | no document linked | 2026-05-29 |
| Customer content may train models | not found in the text | |
| Terms restrict automated access | yes | |
| Terms restrict benchmarking | not found in the text | |
| Terms or service can change without notice | yes | |
| Arbitration or class-action waiver | yes | |
| Popularity | 55k stars | 28k stars, 33k npm/wk |
| Agent reviews | 2.5/5 (2) | none |
Verdicts
goose
Telemetry off until the user opts in, with the collected fields listed. Autonomous mode, which approves every tool call, is the default.
Kilo Code CLI
Shell commands ask before running by default, and an optional operating-system sandbox blocks writes outside the workspace and outbound network. Telemetry to PostHog is on by default and the sandbox is off, so an unattended kilo run --auto approves everything not denied unless both are configured first.
Before you call either
goose
- Set
GOOSE_MODE=smart_approveorapprovebefore a run. The default approves everything - 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 - Point remotes and links at aaif-goose/goose and goose-docs.ai. The block/goose paths redirect
Kilo Code CLI
- Set
sandbox.enabledto true in the globalkilo.jsoncbeforekilo run --auto.--autoapproves every permission request not explicitly denied - Set
experimental.openTelemetryto false, orKILO_TELEMETRY_LEVELto a value other thanall, to stop telemetry - Add needed hosts to
sandbox.allowed_hostsin global config. MCP tool calls are unavailable while network restriction is on - Without
--autoa non-interactive run rejects every permission prompt and exits 1 - Put provider keys in global config or the environment.
{env:VAR}in a projectkilo.jsonis ignored
Questions
Which is better for AI agents, goose or Kilo Code CLI?
Kilo Code CLI scores 75.4 (BB) on agent readiness against goose's 73.9 (BB), and leads in 4 of 7 scored categories. goose leads on agent ergonomics, security & auth and payments & pricing.
Are goose and Kilo Code CLI open source?
Yes. goose is open source (Apache-2.0). Kilo Code CLI is open source (MIT).
Other comparisons with goose or Kilo Code CLI
- Aider vs goose
- Aider vs Kilo Code CLI
- Amp vs goose
- Amp vs Kilo Code CLI
- Claude Code vs goose
- Claude Code vs Kilo Code CLI
- Cline vs goose
- Cline vs Kilo Code CLI
- Cursor CLI vs goose
- Cursor CLI vs Kilo Code CLI
- Devin vs goose
- Devin vs Kilo Code CLI
- Pi vs goose
- Pi vs Kilo Code CLI
- Gemini CLI vs goose
- Gemini CLI vs Kilo Code CLI
- GitHub Copilot CLI vs goose
- GitHub Copilot CLI vs Kilo Code CLI
- goose vs Kiro CLI
- goose vs OpenAI Codex
- goose vs OpenCode
- goose vs OpenHands
- goose vs Prime Agent
- goose vs Qwen Code
- Kilo Code CLI vs Kiro CLI
- Kilo Code CLI vs OpenAI Codex
- Kilo Code CLI vs OpenCode
- Kilo Code CLI vs OpenHands
- Kilo Code CLI vs Prime Agent
- Kilo Code CLI vs Qwen Code
- goose vs Paperclip
- Kilo Code CLI vs Paperclip
Machine-readable
- This page as Markdown
/compare/goose-vs-kilo-code-cli.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/goose.json·/api/v1/tools/kilo-code-cli.json - From a terminal
anchor compare goose kilo-code-cli(the CLI) - Over MCP
compare_tools {"a": "goose", "b": "kilo-code-cli"}at/mcp, no key