Head to head · Agent harness · October 2026 research run
goose vs Kiro CLI
goose scores 73.9 (BB) on agent readiness against Kiro CLI's 59.9 (C), and leads in 6 of 7 scored categories. 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
- Reliability, 77 against 57
- Agent ergonomics, 82 against 67
- Security & auth, 77 against 66
- Payments & pricing, 60 against 40
- Maintenance & community, 86 against 73
Also in its favour
- Agent-ready, a grade of BB or better
- No key needed to call it
- Open source
Watch for
Autonomous mode, which approves every tool call, is the default
Kiro CLI C
Good for Teams on AWS that want one agent configuration across terminal, IDE and web, with central permission policy, prompt logging to their own S3 bucket and IAM Identity Centre sign-in.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
Free and individual paid accounts have content used for service improvement, including model training, unless they opt out
Score by category
| Category | Weight this run | goose | Kiro CLI | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 77 | 57 | goose +20 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 81 | 79 | goose +2 |
| Agent ergonomics | 13%16.2 | 82 | 67 | goose +15 |
| Security & auth | 14%17.5 | 77 | 66 | goose +11 |
| Payments & pricing | 10%12.5 | 60 | 40 | goose +20 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 86 | 73 | goose +13 |
| Transparency & trust | 7%8.8 | 63 | 67 | Kiro CLI +4 |
| Negative events | ≤15 | -2 | -4 | |
| Total | 73.9 · BB | 59.9 · C |
Facts side by side
| Fact | goose | Kiro CLI |
|---|---|---|
| Kind | Agent harness | Agent harness |
| Vendor | Agentic AI Foundation (originally Block) | Amazon Web Services |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 | Proprietary. Licensed as AWS Content under the AWS Customer Agreement and the AWS Intellectual Property Licence (https://kiro.dev/license/). The GitHub repository is the public issue tracker and doesn't hold the source |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-23 | 2026-10-05 |
| Terms last updated | no document linked | 2026-08-14 |
| Privacy policy last updated | no document linked | 2026-05-18 |
| Customer content may train models | not found in the text | |
| Terms restrict automated access | not found in the text | |
| Terms restrict benchmarking | not found in the text | |
| Terms or service can change without notice | not found in the text | |
| Arbitration or class-action waiver | yes | |
| Popularity | 55k stars | 4.4k stars |
| 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.
Kiro CLI
Permission rules follow deny over ask over allow, cloned repositories can't add rules, and a headless session treats every ask as a deny. Content from Free and individual paid accounts is used for service improvement, including model training, unless the user opts out, and API keys for pipelines need a paid plan.
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
Kiro CLI
- Set
KIRO_API_KEYand pass--no-interactivewith--trust-tools=<list>in pipelines. Keep--trust-all-toolsfor disposable environments - Pass
--require-mcp-startupwhen a run depends on MCP tools. Without it a failed server is logged and the run continues - Pass
--no-interactivewhenever input is piped from a source you don't control, and run 2.10.0 or later on Windows - Run
kiro-cli settings telemetry.enabled falseand turn off content collection on Free and individual plans. Both are on by default - Export variables in the shell before starting. Since 2.24.0 a project
.envfile is no longer loaded into sessions, MCP servers or tools
Questions
Which is better for AI agents, goose or Kiro CLI?
goose scores 73.9 (BB) on agent readiness against Kiro CLI's 59.9 (C), and leads in 6 of 7 scored categories.
Are goose and Kiro CLI open source?
goose is open source (Apache-2.0). No open-source release is listed for Kiro CLI.
Other comparisons with goose or Kiro CLI
- Aider vs goose
- Aider vs Kiro CLI
- Amp vs goose
- Amp vs Kiro CLI
- Claude Code vs goose
- Claude Code vs Kiro CLI
- Cline vs goose
- Cline vs Kiro CLI
- Cursor CLI vs goose
- Cursor CLI vs Kiro CLI
- Devin vs goose
- Devin vs Kiro CLI
- Pi vs goose
- Pi vs Kiro CLI
- Gemini CLI vs goose
- Gemini CLI vs Kiro CLI
- GitHub Copilot CLI vs goose
- GitHub Copilot CLI vs Kiro CLI
- goose vs OpenAI Codex
- goose vs OpenCode
- goose vs OpenHands
- goose vs Prime Agent
- goose vs Qwen Code
- Kiro CLI vs OpenAI Codex
- Kiro CLI vs OpenCode
- Kiro CLI vs OpenHands
- Kiro CLI vs Prime Agent
- Kiro CLI vs Qwen Code
- goose vs Paperclip
- Kiro CLI vs Paperclip
Machine-readable
- This page as Markdown
/compare/goose-vs-kiro-cli.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/goose.json·/api/v1/tools/kiro-cli.json - From a terminal
anchor compare goose kiro-cli(the CLI) - Over MCP
compare_tools {"a": "goose", "b": "kiro-cli"}at/mcp, no key