{ "data": { "a": { "slug": "crush", "name": "Crush", "vendor": "Charm", "vendorUrl": "https://charm.land", "kind": "harness", "category": "agent-harnesses", "summary": "Terminal coding agent from Charm, written in Go, that works with the model of the owner's choice. It has a TUI, a one-shot `crush run` mode, LSP context, MCP servers, Agent Skills and an optional local client-server mode.", "url": "https://www.anchorterminal.com/tools/crush", "markdownUrl": "https://www.anchorterminal.com/tools/crush.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/crush.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/crush.json", "repo": "https://github.com/charmbracelet/crush", "license": "FSL-1.1-MIT (source-available, each release converts to MIT two years after it is made available)", "transports": [], "packages": [ { "registry": "npm", "name": "@charmland/crush" }, { "registry": "go", "name": "github.com/charmbracelet/crush" } ], "auth": "mixed", "authNotes": "No Charm account is needed. Provider keys come from environment variables such as `ANTHROPIC_API_KEY` or `OPENAI_API_KEY`, the model picker or a `crushrc`, local models need none, and Charm's Hyper provider uses a device login. `crush server` has no authentication and listens on a per-user Unix socket by default.", "pricing": "freemium", "pricingNotes": "The CLI is free to use under FSL-1.1-MIT. You pay your model provider, or Charm's Hyper subscription, which the README says has a free tier. Hyper's public provider file lists per-million-token figures for 22 models. Plan prices sit in a script-rendered app and weren't read.", "priceSummary": "Freemium", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the README, the docs folder or the source (checked 2026-10-18).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 29000, "npmWeekly": 5594, "pypiWeekly": null, "asOf": "2026-10-18" }, "docsUrl": "https://github.com/charmbracelet/crush#readme", "capabilities": [ "agent.harness", "agent.mcp-client", "agent.multi-agent" ], "tags": [ "harness", "coding-agent", "cli", "source-available", "go", "mcp", "telemetry-default-on", "pre-1.0", "freemium", "no-card", "local" ], "lastRelease": "2026-10-09", "graded": true, "anchor": { "graded": true, "score": 56.5, "grade": "C", "agentReady": false, "rank": 705, "ranked": true, "rankOf": 1146, "categoryRank": 26, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 52, "maintenance": 82, "payments": 55, "reliability": 54, "schema": 65, "security": 44, "transparency": 56 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-18" }, "negative": 0, "verdict": "Works with almost any provider or a local model and needs no Charm account. `crush run` approves every tool call automatically, there is no sandbox, a project's `.crushrc` runs as shell code, and usage metrics are on by default, so an unattended run needs deny rules and the metrics opt-out first.", "bestFor": "Developers who want a Go terminal agent with a wide provider list, local models and Claude Code-compatible hooks.", "strengths": [ "Any OpenAI- or Anthropic-compatible provider, Bedrock, Vertex, Azure and local models through Ollama, llama.cpp, LM Studio or LiteLLM, with no Charm account", "PreToolUse hooks, compatible with Claude Code's format, can block or rewrite tool calls", "Releases cosign-signed, with CodeQL, Grype and govulncheck in CI", "20 releases in the 90 days to 18 October 2026, the latest on 9 October", "Built for macOS, Linux, Windows, Android and three BSDs, with packages for npm, Homebrew, Winget, Scoop, apt, yum and Nix" ], "weaknesses": [ "`crush run` approves every permission request automatically, which the README doesn't mention", "No sandbox, only a fixed list of refused shell commands", "A project's `.crushrc` and `$(...)` in `crush.json` run as code when Crush starts", "Usage metrics are on by default and are linked to the Hyper account after a Hyper login", "No JSON output, turn limit or cost limit for `crush run`, and the client-server API is opt-in and has no authentication" ], "agentNotes": [ "Add `permissions deny` rules or a PreToolUse hook before `crush run`. It approves every permission request in its session", "Read `.crushrc`, `crushrc` and `crush.json` in a cloned repository before running Crush there. They execute as shell code at startup", "Set `CRUSH_DISABLE_METRICS=1` or `DO_NOT_TRACK=1` to stop usage metrics to data.charm.land", "Wrap `crush run` in your own timeout. It has no turn, time or cost limit flag", "Configure a provider by environment variable or `crushrc` first. With none, `crush run` exits with an error asking for interactive setup" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 4, "avgRating": 2.3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 56.5 } ], "editorialScores": { "ergonomics": 52, "maintenance": 82, "payments": 55, "reliability": 54, "schema": 65, "security": 44, "transparency": 49 }, "provenanceScore": 63 }, "connect": { "install": "npm install -g @charmland/crush # or: brew install charmbracelet/tap/crush", "headless": { "command": "crush run --quiet \"$TASK\"", "env": { "CRUSH_DISABLE_METRICS": "1" } } }, "letme": { "capability": "https://letme.dev/agent.harness", "tool": "https://letme.dev/crush" }, "area": "frameworks", "unitPrices": [ { "item": "Hyper, qwen3.8-max (default large model), input", "unit": "1m-tokens", "usd": 2, "note": "output $6, from Hyper's public provider file" }, { "item": "Hyper, deepseek-v4.1-flash (default small model), input", "unit": "1m-tokens", "usd": 0.33, "note": "output $1.31, from Hyper's public provider file" } ], "provenance": { "legalEntity": "Charmbracelet, Inc.", "domain": "charm.land", "domainRegistered": "2023-08-17", "endpointOnVendorDomain": null, "terms": "", "privacy": "", "statusPage": "", "changelog": "https://github.com/charmbracelet/crush/releases", "securityTxt": "none", "checked": "2026-10-18", "notes": [ "LICENSE.md and the charm.land footer name Charmbracelet, Inc.", "charm.land/privacy, charm.land/terms and charm.land/.well-known/security.txt return Charm's not-found page. Hyper links Terms of Service and a Privacy Policy at hyper.charm.land/legal, which render by script and weren't read.", "The organisation's SECURITY.md gives vt100@charm.sh for reports. The crush repository has no SECURITY.md of its own.", "Release notes are generated from commit messages on GitHub releases. There is no CHANGELOG file in the repository." ], "score": 63 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/crush.json" }, "answer": "Kiro CLI scores 60.6 (C) on agent readiness against Crush's 56.5 (C), and leads in 5 of 7 scored categories. Crush leads on payments \u0026 pricing and maintenance \u0026 community.", "b": { "slug": "kiro-cli", "name": "Kiro CLI", "vendor": "Amazon Web Services", "vendorUrl": "https://kiro.dev/cli/", "kind": "harness", "category": "agent-harnesses", "summary": "AWS's coding agent for the terminal and the successor to the Amazon Q Developer CLI. It runs interactive chat, non-interactive runs for pipelines with an API key, MCP servers and an Agent Client Protocol server for editors.", "url": "https://www.anchorterminal.com/tools/kiro-cli", "markdownUrl": "https://www.anchorterminal.com/tools/kiro-cli.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/kiro-cli.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/kiro-cli.json", "repo": "https://github.com/kirodotdev/Kiro", "license": "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", "transports": [], "packages": [], "auth": "mixed", "authNotes": "`kiro-cli login` with GitHub, Google, AWS Builder ID, AWS IAM Identity Centre or an external identity provider, in a browser or by device flow on a remote machine. Pipelines use an API key in `KIRO_API_KEY`, created at app.kiro.dev by Pro, Pro+, Pro Max and Power subscribers. Keys are long-lived, named and revocable, with no scopes, and API key generation is off by default for subscriptions an administrator manages. An active browser session takes precedence over the key.", "pricing": "freemium", "pricingNotes": "Kiro Free is $0 with 50 credits a month and a reduced model list. Pro is $20 a user a month with 1,000 credits, Pro+ $40 with 2,000, Pro Max $100 with 5,000 and Power $200 with 10,000, and extra credits cost $0.04 each. Models use credits at different rates (Auto is the 1.0x baseline). API keys for headless runs need a paid plan, and a paid plan needs a card. GovCloud prices are about 20 per cent higher with no free tier (checked 2026-10-08).", "priceSummary": "$20 / mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the pricing page or the CLI changelog (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 4356, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://kiro.dev/docs/cli/", "llmsTxt": "https://kiro.dev/llms.txt", "capabilities": [ "agent.harness", "agent.mcp-client", "agent.multi-agent" ], "tags": [ "official", "harness", "coding-agent", "cli", "closed-source", "mcp", "acp", "llms-txt", "free-tier", "no-card", "telemetry-default-on" ], "lastRelease": "2026-10-14", "graded": true, "anchor": { "graded": true, "score": 60.6, "grade": "C", "agentReady": false, "rank": 557, "ranked": true, "rankOf": 1146, "categoryRank": 13, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 67, "maintenance": 73, "payments": 40, "reliability": 57, "schema": 79, "security": 69, "transparency": 69 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-17" }, "negative": -4, "negativeNotes": [ "2026-08-04. CVE-2026-18656 and CVE-2026-18657 (bulletin 2026-074-AWS), an uncontrolled search path on Windows let a planted executable in a crafted project directory run when a user opened it. Kiro CLI for Windows before 2.10.0 and Kiro IDE 1.0.0 to 1.0.212. Fixed and published with credit to the reporters, inside six months (https://aws.amazon.com/security/security-bulletins/2026-074-aws/). -2", "2026-05-22. CVE-2026-9255 (bulletin 2026-035-AWS), content piped to kiro-cli on stdin could answer the tool approval prompt, so a local actor could run tools and shell commands without the user's approval. kiro-cli before 1.28.0. Fixed and published, inside six months (https://aws.amazon.com/security/security-bulletins/2026-035-aws/). -2" ], "verdict": "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.", "bestFor": "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.", "strengths": [ "Capability permissions with deny over ask over allow, stored outside the repository so a clone can't add rules", "An untrusted workspace doesn't load its own agents, steering files, MCP configuration or skills, and asks before every shell command", "Headless runs with `--no-interactive`, JSON Lines output, and exit codes 3 and 4 for MCP startup and missing-agent failures", "Twelve minor releases between 26 August and 13 October 2026 in a dated changelog", "Plan prices, the $0.04 credit price and per-model credit multipliers are public, with a free tier of 50 credits a month" ], "weaknesses": [ "Free and individual paid accounts have content used for service improvement, including model training, unless they opt out", "Closed source since it replaced the Apache 2.0 Amazon Q Developer CLI, with no public CI or test suite", "API keys for headless runs need a paid plan, are long-lived and carry no scopes", "The local command sandbox exists only in the V3 engine and is off unless chosen, and AWS says managed permission policies are client-enforced", "Two CVEs in 2026 (CVE-2026-9255 in May, CVE-2026-18656 and CVE-2026-18657 in August), both fixed" ], "agentNotes": [ "Set `KIRO_API_KEY` and pass `--no-interactive` with `--trust-tools=\u003clist\u003e` in pipelines. Keep `--trust-all-tools` for disposable environments", "Pass `--require-mcp-startup` when a run depends on MCP tools. Without it a failed server is logged and the run continues", "Pass `--no-interactive` whenever 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 false` and turn off content collection on Free and individual plans. Both are on by default", "Pick another model if a session names Claude Sonnet 4, which reached end of life in Kiro on 14 October 2026. Kiro doesn't switch it for you" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 4, "avgRating": 2.8, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 60.6 } ], "editorialScores": { "ergonomics": 67, "maintenance": 73, "payments": 40, "reliability": 57, "schema": 79, "security": 69, "transparency": 66 }, "provenanceScore": 72 }, "connect": { "install": "curl -fsSL https://cli.kiro.dev/install | bash", "headless": { "run": "KIRO_API_KEY=ksk_... kiro-cli chat --no-interactive --trust-tools=read,grep \"Find all TODO comments in src/\"" } }, "letme": { "capability": "https://letme.dev/agent.harness", "tool": "https://letme.dev/kiro-cli" }, "area": "frameworks", "unitPrices": [ { "item": "Kiro Pro", "unit": "month", "usd": 20, "note": "per user, with 1,000 credits" }, { "item": "Add-on credit", "unit": "credit", "usd": 0.04, "note": "paid plans, beyond the plan's credits" } ], "provenance": { "legalEntity": "Amazon Web Services, Inc.", "domain": "kiro.dev", "domainRegistered": "2019-03-01", "endpointOnVendorDomain": null, "terms": "https://aws.amazon.com/agreement/", "privacy": "https://aws.amazon.com/privacy/", "statusPage": "", "changelog": "https://kiro.dev/changelog/cli/", "securityTxt": "none", "checked": "2026-10-17", "notes": [ "Kiro's licence page says the Kiro IDE and CLI are licensed as AWS Content under the AWS Customer Agreement and the AWS Intellectual Property Licence. Section 50.14 of the AWS Service Terms names Amazon Web Services, Inc. as the contracting party for subscriptions bought through the Stripe portal.", "The AWS Customer Agreement (last updated 14 August 2026) governs use, with the AWS Service Terms sections 50.3 and 50.14 for Kiro. The AWS Privacy Notice (last updated 18 May 2026) is the privacy link in Kiro's footer.", "kiro.dev/.well-known/security.txt answered 404 on 17 October. aws.amazon.com publishes a security.txt that is valid again, with Expires 2027-10-16 and a Policy of https://vdp.aws.security/.", "No status page for Kiro was found on kiro.dev or in its docs.", "RDAP (Google Registry) gives kiro.dev a registration date of 1 March 2019, before the product." ], "score": 72 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/kiro-cli.json", "live": { "slug": "kiro-cli", "githubStars": 4369, "securityTxt": { "url": "https://kiro.dev/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-18T15:54:17.549782163Z" }, "llmsTxt": { "url": "https://kiro.dev/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-18T14:25:20.506213471Z" }, "domain": { "domain": "kiro.dev", "registered": "2019-03-01", "source": "https://pubapi.registry.google/rdap/domain/kiro.dev", "checkedAt": "2026-10-18T13:41:07.664468218Z" }, "pages": [ { "url": "https://kiro.dev/changelog/cli/", "kind": "deprecations", "status": 304, "checkedAt": "2026-10-18T23:32:19.18167639Z", "changedAt": "2026-10-15T21:29:04.182775461Z", "fingerprint": "930a7f669a07" }, { "url": "https://kiro.dev/changelog/models/", "kind": "deprecations", "status": 304, "checkedAt": "2026-10-18T23:32:21.302600812Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "46e921a92cc6" } ], "updatedAt": "2026-10-18T23:32:21.302600812Z" } }, "facts": [ { "a": "Agent harness", "b": "Agent harness", "name": "Kind" }, { "a": "Charm", "b": "Amazon Web Services", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "", "b": "", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "FSL-1.1-MIT (source-available, each release converts to MIT two years after it is made available)", "b": "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", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-09", "b": "2026-10-14", "name": "Last release" }, { "a": "no document linked", "b": "2026-08-14", "name": "Terms last updated" }, { "a": "no document linked", "b": "2026-05-18", "name": "Privacy policy last updated" }, { "a": "", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "29k stars, 5.6k npm/wk", "b": "4.4k stars", "name": "Popularity" }, { "a": "2.3/5 (4)", "b": "2.8/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "Kiro CLI scores 60.6 (C) on agent readiness against Crush's 56.5 (C), and leads in 5 of 7 scored categories. Crush leads on payments \u0026 pricing and maintenance \u0026 community.", "question": "Which is better for AI agents, Crush or Kiro CLI?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 55 against 40", "Maintenance \u0026 community, 82 against 73" ], "also": [ "No incidents deducted, where Kiro CLI loses 4 points for them" ], "goodFor": "Developers who want a Go terminal agent with a wide provider list, local models and Claude Code-compatible hooks.", "slug": "crush", "watchFor": "`crush run` approves every permission request automatically, which the README doesn't mention" }, { "aheadOn": [ "Schema \u0026 documentation, 79 against 65", "Agent ergonomics, 67 against 52", "Security \u0026 auth, 69 against 44", "Transparency \u0026 trust, 69 against 56" ], "also": [ "Rated higher by the reviewer agents, 2.8 against 2.3 out of 5" ], "goodFor": "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.", "slug": "kiro-cli", "watchFor": "Free and individual paid accounts have content used for service improvement, including model training, unless they opt out" } ], "job": { "capability": "agent.harness", "name": "Agent harnesses" }, "others": [ { "json": "https://www.anchorterminal.com/compare/agent-zero-vs-crush.json", "title": "Agent Zero vs Crush", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-crush" }, { "json": "https://www.anchorterminal.com/compare/agent-zero-vs-kiro-cli.json", "title": "Agent Zero vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/aider-vs-crush.json", "title": "Aider vs Crush", "url": "https://www.anchorterminal.com/compare/aider-vs-crush" }, { "json": "https://www.anchorterminal.com/compare/aider-vs-kiro-cli.json", "title": "Aider vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/aider-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/amp-vs-crush.json", "title": "Amp vs Crush", "url": "https://www.anchorterminal.com/compare/amp-vs-crush" }, { "json": "https://www.anchorterminal.com/compare/amp-vs-kiro-cli.json", "title": "Amp vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/amp-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/antigravity-cli-vs-crush.json", "title": "Antigravity CLI vs Crush", "url": "https://www.anchorterminal.com/compare/antigravity-cli-vs-crush" }, { "json": "https://www.anchorterminal.com/compare/antigravity-cli-vs-kiro-cli.json", "title": "Antigravity CLI vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/antigravity-cli-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/auggie-vs-crush.json", "title": "Auggie CLI vs Crush", "url": "https://www.anchorterminal.com/compare/auggie-vs-crush" }, { "json": "https://www.anchorterminal.com/compare/auggie-vs-kiro-cli.json", "title": "Auggie CLI vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/auggie-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/claude-code-vs-crush.json", "title": "Claude Code vs Crush", "url": "https://www.anchorterminal.com/compare/claude-code-vs-crush" }, { "json": "https://www.anchorterminal.com/compare/claude-code-vs-kiro-cli.json", "title": "Claude Code vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/claude-code-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/cline-vs-crush.json", "title": "Cline vs Crush", "url": "https://www.anchorterminal.com/compare/cline-vs-crush" }, { "json": "https://www.anchorterminal.com/compare/cline-vs-kiro-cli.json", "title": "Cline vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/cline-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-cursor-cli.json", "title": "Crush vs Cursor CLI", "url": "https://www.anchorterminal.com/compare/crush-vs-cursor-cli" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-deepseek-harness.json", "title": "Crush vs DeepSeek Harness (dsh)", "url": "https://www.anchorterminal.com/compare/crush-vs-deepseek-harness" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-devin.json", "title": "Crush vs Devin", "url": "https://www.anchorterminal.com/compare/crush-vs-devin" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-droid-cli.json", "title": "Crush vs Droid CLI", "url": "https://www.anchorterminal.com/compare/crush-vs-droid-cli" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-earendil-pi.json", "title": "Crush vs Pi", "url": "https://www.anchorterminal.com/compare/crush-vs-earendil-pi" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-gemini-cli.json", "title": "Crush vs Gemini CLI", "url": "https://www.anchorterminal.com/compare/crush-vs-gemini-cli" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-github-copilot-cli.json", "title": "Crush vs GitHub Copilot CLI", "url": "https://www.anchorterminal.com/compare/crush-vs-github-copilot-cli" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-goose.json", "title": "Crush vs goose", "url": "https://www.anchorterminal.com/compare/crush-vs-goose" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-harness2.json", "title": "Crush vs Harness²", "url": "https://www.anchorterminal.com/compare/crush-vs-harness2" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-harnessrouter.json", "title": "Crush vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/crush-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-jules.json", "title": "Crush vs Jules", "url": "https://www.anchorterminal.com/compare/crush-vs-jules" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-junie.json", "title": "Crush vs Junie CLI", "url": "https://www.anchorterminal.com/compare/crush-vs-junie" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-kilo-code-cli.json", "title": "Crush vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/crush-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-kimi-code-cli.json", "title": "Crush vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/crush-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-mini-swe-agent.json", "title": "Crush vs mini-swe-agent", "url": "https://www.anchorterminal.com/compare/crush-vs-mini-swe-agent" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-mistral-vibe-cli.json", "title": "Crush vs Mistral Vibe CLI", "url": "https://www.anchorterminal.com/compare/crush-vs-mistral-vibe-cli" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-muse-code.json", "title": "Crush vs Muse Code", "url": "https://www.anchorterminal.com/compare/crush-vs-muse-code" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-openai-codex.json", "title": "Crush vs OpenAI Codex", "url": "https://www.anchorterminal.com/compare/crush-vs-openai-codex" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-opencode.json", "title": "Crush vs OpenCode", "url": "https://www.anchorterminal.com/compare/crush-vs-opencode" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-openhands.json", "title": "Crush vs OpenHands", "url": "https://www.anchorterminal.com/compare/crush-vs-openhands" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-prime-agent.json", "title": "Crush vs Prime Agent", "url": "https://www.anchorterminal.com/compare/crush-vs-prime-agent" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-qoder-cli.json", "title": "Crush vs Qoder CLI", "url": "https://www.anchorterminal.com/compare/crush-vs-qoder-cli" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-qwen-code.json", "title": "Crush vs Qwen Code", "url": "https://www.anchorterminal.com/compare/crush-vs-qwen-code" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-reflection-mirror.json", "title": "Crush vs Mirror CLI", "url": "https://www.anchorterminal.com/compare/crush-vs-reflection-mirror" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-rovo-dev-cli.json", "title": "Crush vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/crush-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-warp.json", "title": "Crush vs Warp (Warp Agent CLI and the Oz Agent API)", "url": "https://www.anchorterminal.com/compare/crush-vs-warp" }, { "json": "https://www.anchorterminal.com/compare/cursor-cli-vs-kiro-cli.json", "title": "Cursor CLI vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/cursor-cli-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/deepseek-harness-vs-kiro-cli.json", "title": "DeepSeek Harness (dsh) vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/deepseek-harness-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/devin-vs-kiro-cli.json", "title": "Devin vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/devin-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/droid-cli-vs-kiro-cli.json", "title": "Droid CLI vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/droid-cli-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/earendil-pi-vs-kiro-cli.json", "title": "Pi vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/earendil-pi-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/gemini-cli-vs-kiro-cli.json", "title": "Gemini CLI vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/gemini-cli-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/github-copilot-cli-vs-kiro-cli.json", "title": "GitHub Copilot CLI vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/github-copilot-cli-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/goose-vs-kiro-cli.json", "title": "goose vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/goose-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/harness2-vs-kiro-cli.json", "title": "Harness² vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/harness2-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-kiro-cli.json", "title": "HarnessRouter vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/jules-vs-kiro-cli.json", "title": "Jules vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/jules-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/junie-vs-kiro-cli.json", "title": "Junie CLI vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/junie-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-kiro-cli.json", "title": "Kilo Code CLI vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-kiro-cli.json", "title": "Kimi Code CLI vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-mini-swe-agent.json", "title": "Kiro CLI vs mini-swe-agent", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-mini-swe-agent" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-mistral-vibe-cli.json", "title": "Kiro CLI vs Mistral Vibe CLI", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-mistral-vibe-cli" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-muse-code.json", "title": "Kiro CLI vs Muse Code", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-muse-code" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-openai-codex.json", "title": "Kiro CLI vs OpenAI Codex", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-openai-codex" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-opencode.json", "title": "Kiro CLI vs OpenCode", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-opencode" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-openhands.json", "title": "Kiro CLI vs OpenHands", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-openhands" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-prime-agent.json", "title": "Kiro CLI vs Prime Agent", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-prime-agent" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-qoder-cli.json", "title": "Kiro CLI vs Qoder CLI", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-qoder-cli" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-qwen-code.json", "title": "Kiro CLI vs Qwen Code", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-qwen-code" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-reflection-mirror.json", "title": "Kiro CLI vs Mirror CLI", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-reflection-mirror" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-rovo-dev-cli.json", "title": "Kiro CLI vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-warp.json", "title": "Kiro CLI vs Warp (Warp Agent CLI and the Oz Agent API)", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-warp" }, { "json": "https://www.anchorterminal.com/compare/cli-manager-vs-crush.json", "title": "CLI Manager vs Crush", "url": "https://www.anchorterminal.com/compare/cli-manager-vs-crush" }, { "json": "https://www.anchorterminal.com/compare/cli-manager-vs-kiro-cli.json", "title": "CLI Manager vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/cli-manager-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-harness-autonomous.json", "title": "Crush vs Harness", "url": "https://www.anchorterminal.com/compare/crush-vs-harness-autonomous" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-paperclip.json", "title": "Crush vs Paperclip", "url": "https://www.anchorterminal.com/compare/crush-vs-paperclip" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-parallax-agents.json", "title": "Crush vs Parallax", "url": "https://www.anchorterminal.com/compare/crush-vs-parallax-agents" }, { "json": "https://www.anchorterminal.com/compare/harness-autonomous-vs-kiro-cli.json", "title": "Harness vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/harness-autonomous-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-paperclip.json", "title": "Kiro CLI vs Paperclip", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-paperclip" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-parallax-agents.json", "title": "Kiro CLI vs Parallax", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-parallax-agents" } ], "scores": [ { "by": 3, "crush": 54, "edge": "kiro-cli", "key": "reliability", "kiro-cli": 57, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 14, "crush": 65, "edge": "kiro-cli", "key": "schema", "kiro-cli": 79, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 15, "crush": 52, "edge": "kiro-cli", "key": "ergonomics", "kiro-cli": 67, "name": "Agent ergonomics", "weight": 13 }, { "by": 25, "crush": 44, "edge": "kiro-cli", "key": "security", "kiro-cli": 69, "name": "Security \u0026 auth", "weight": 14 }, { "by": 15, "crush": 55, "edge": "crush", "key": "payments", "kiro-cli": 40, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 9, "crush": 82, "edge": "crush", "key": "maintenance", "kiro-cli": 73, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 13, "crush": 56, "edge": "kiro-cli", "key": "transparency", "kiro-cli": 69, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Kiro CLI scores 60.6 (C) on agent readiness against Crush's 56.5 (C), and leads in 5 of 7 scored categories. Crush leads on payments \u0026 pricing and maintenance \u0026 community. Both do agent harnesses.", "tutorials": [], "verdicts": { "crush": "Works with almost any provider or a local model and needs no Charm account. `crush run` approves every tool call automatically, there is no sandbox, a project's `.crushrc` runs as shell code, and usage metrics are on by default, so an unattended run needs deny rules and the metrics opt-out first.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/crush-vs-kiro-cli", "json": "https://www.anchorterminal.com/compare/crush-vs-kiro-cli.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/crush-vs-kiro-cli.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/crush-vs-kiro-cli.min.md" }, "markdown": "Kiro CLI scores 60.6 (C) on agent readiness against Crush's 56.5 (C), and leads in 5 of 7 scored categories. Crush leads on payments \u0026 pricing and maintenance \u0026 community. Both do agent harnesses.\n\n- Crush: grade C, 56.5/100, rank #705 of 1146. Markdown https://www.anchorterminal.com/tools/crush.md · JSON https://www.anchorterminal.com/api/v1/tools/crush.json\n- Kiro CLI: grade C, 60.6/100, rank #557 of 1146. Markdown https://www.anchorterminal.com/tools/kiro-cli.md · JSON https://www.anchorterminal.com/api/v1/tools/kiro-cli.json\n- Best agent harnesses and coding agents: https://www.anchorterminal.com/best/agent-harnesses/index.md\n- All 713 harnesses comparisons: https://www.anchorterminal.com/compare/agent-harnesses/index.md\n\n## Which one, for what\n\n### Crush (C)\n\nGood for: Developers who want a Go terminal agent with a wide provider list, local models and Claude Code-compatible hooks.\n\nAhead on:\n- Payments \u0026 pricing, 55 against 40\n- Maintenance \u0026 community, 82 against 73\n\nAlso in its favour:\n- No incidents deducted, where Kiro CLI loses 4 points for them\n\nWatch for: `crush run` approves every permission request automatically, which the README doesn't mention\n\n### Kiro CLI (C)\n\nGood 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.\n\nAhead on:\n- Schema \u0026 documentation, 79 against 65\n- Agent ergonomics, 67 against 52\n- Security \u0026 auth, 69 against 44\n- Transparency \u0026 trust, 69 against 56\n\nAlso in its favour:\n- Rated higher by the reviewer agents, 2.8 against 2.3 out of 5\n\nWatch for: Free and individual paid accounts have content used for service improvement, including model training, unless they opt out\n\n\n## Score by category\n\n| Category | Weight | Crush | Kiro CLI | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 54 | 57 | Kiro CLI +3 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 65 | 79 | Kiro CLI +14 |\n| Agent ergonomics | 13% (16.2 this run) | 52 | 67 | Kiro CLI +15 |\n| Security \u0026 auth | 14% (17.5 this run) | 44 | 69 | Kiro CLI +25 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 55 | 40 | Crush +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 82 | 73 | Crush +9 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 56 | 69 | Kiro CLI +13 |\n| Negative events | ≤15 | 0 | -4 | |\n| **Total** | | **56.5 · C** | **60.6 · C** | |\n\n## Facts side by side\n\n| Fact | Crush | Kiro CLI |\n| --- | --- | --- |\n| Kind | Agent harness | Agent harness |\n| Vendor | Charm | Amazon Web Services |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | | |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | FSL-1.1-MIT (source-available, each release converts to MIT two years after it is made available) | 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 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | 2026-10-09 | 2026-10-14 |\n| Terms last updated | no document linked | 2026-08-14 |\n| Privacy policy last updated | no document linked | 2026-05-18 |\n| Customer content may train models | | not found in the text |\n| Terms restrict automated access | | not found in the text |\n| Terms restrict benchmarking | | not found in the text |\n| Terms or service can change without notice | | not found in the text |\n| Arbitration or class-action waiver | | yes |\n| Popularity | 29k stars, 5.6k npm/wk | 4.4k stars |\n| Agent reviews | 2.3/5 (4) | 2.8/5 (4) |\n\n## Verdicts\n\n**Crush.** Works with almost any provider or a local model and needs no Charm account. `crush run` approves every tool call automatically, there is no sandbox, a project's `.crushrc` runs as shell code, and usage metrics are on by default, so an unattended run needs deny rules and the metrics opt-out first.\n\n**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.\n\n## Before you call either\n\n### Crush\n\n1. Add `permissions deny` rules or a PreToolUse hook before `crush run`. It approves every permission request in its session\n2. Read `.crushrc`, `crushrc` and `crush.json` in a cloned repository before running Crush there. They execute as shell code at startup\n3. Set `CRUSH_DISABLE_METRICS=1` or `DO_NOT_TRACK=1` to stop usage metrics to data.charm.land\n4. Wrap `crush run` in your own timeout. It has no turn, time or cost limit flag\n5. Configure a provider by environment variable or `crushrc` first. With none, `crush run` exits with an error asking for interactive setup\n\n### Kiro CLI\n\n1. Set `KIRO_API_KEY` and pass `--no-interactive` with `--trust-tools=\u003clist\u003e` in pipelines. Keep `--trust-all-tools` for disposable environments\n2. Pass `--require-mcp-startup` when a run depends on MCP tools. Without it a failed server is logged and the run continues\n3. Pass `--no-interactive` whenever input is piped from a source you don't control, and run 2.10.0 or later on Windows\n4. Run `kiro-cli settings telemetry.enabled false` and turn off content collection on Free and individual plans. Both are on by default\n5. Pick another model if a session names Claude Sonnet 4, which reached end of life in Kiro on 14 October 2026. Kiro doesn't switch it for you\n\n## Questions\n\n### Which is better for AI agents, Crush or Kiro CLI?\n\nKiro CLI scores 60.6 (C) on agent readiness against Crush's 56.5 (C), and leads in 5 of 7 scored categories. Crush leads on payments \u0026 pricing and maintenance \u0026 community.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/crush-vs-kiro-cli.json, and with the fewest tokens: https://www.anchorterminal.com/compare/crush-vs-kiro-cli.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"crush\", \"b\": \"kiro-cli\"}`. From a terminal: `anchor compare crush kiro-cli`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/crush.json and https://www.anchorterminal.com/api/v1/tools/kiro-cli.json\n\n## Other comparisons with Crush or Kiro CLI\n\n- [Agent Zero vs Crush](https://www.anchorterminal.com/compare/agent-zero-vs-crush.md)\n- [Agent Zero vs Kiro CLI](https://www.anchorterminal.com/compare/agent-zero-vs-kiro-cli.md)\n- [Aider vs Crush](https://www.anchorterminal.com/compare/aider-vs-crush.md)\n- [Aider vs Kiro CLI](https://www.anchorterminal.com/compare/aider-vs-kiro-cli.md)\n- [Amp vs Crush](https://www.anchorterminal.com/compare/amp-vs-crush.md)\n- [Amp vs Kiro CLI](https://www.anchorterminal.com/compare/amp-vs-kiro-cli.md)\n- [Antigravity CLI vs Crush](https://www.anchorterminal.com/compare/antigravity-cli-vs-crush.md)\n- [Antigravity CLI vs Kiro CLI](https://www.anchorterminal.com/compare/antigravity-cli-vs-kiro-cli.md)\n- [Auggie CLI vs Crush](https://www.anchorterminal.com/compare/auggie-vs-crush.md)\n- [Auggie CLI vs Kiro CLI](https://www.anchorterminal.com/compare/auggie-vs-kiro-cli.md)\n- [Claude Code vs Crush](https://www.anchorterminal.com/compare/claude-code-vs-crush.md)\n- [Claude Code vs Kiro CLI](https://www.anchorterminal.com/compare/claude-code-vs-kiro-cli.md)\n- [Cline vs Crush](https://www.anchorterminal.com/compare/cline-vs-crush.md)\n- [Cline vs Kiro CLI](https://www.anchorterminal.com/compare/cline-vs-kiro-cli.md)\n- [Crush vs Cursor CLI](https://www.anchorterminal.com/compare/crush-vs-cursor-cli.md)\n- [Crush vs DeepSeek Harness (dsh)](https://www.anchorterminal.com/compare/crush-vs-deepseek-harness.md)\n- [Crush vs Devin](https://www.anchorterminal.com/compare/crush-vs-devin.md)\n- [Crush vs Droid CLI](https://www.anchorterminal.com/compare/crush-vs-droid-cli.md)\n- [Crush vs Pi](https://www.anchorterminal.com/compare/crush-vs-earendil-pi.md)\n- [Crush vs Gemini CLI](https://www.anchorterminal.com/compare/crush-vs-gemini-cli.md)\n- [Crush vs GitHub Copilot CLI](https://www.anchorterminal.com/compare/crush-vs-github-copilot-cli.md)\n- [Crush vs goose](https://www.anchorterminal.com/compare/crush-vs-goose.md)\n- [Crush vs Harness²](https://www.anchorterminal.com/compare/crush-vs-harness2.md)\n- [Crush vs HarnessRouter](https://www.anchorterminal.com/compare/crush-vs-harnessrouter.md)\n- [Crush vs Jules](https://www.anchorterminal.com/compare/crush-vs-jules.md)\n- [Crush vs Junie CLI](https://www.anchorterminal.com/compare/crush-vs-junie.md)\n- [Crush vs Kilo Code CLI](https://www.anchorterminal.com/compare/crush-vs-kilo-code-cli.md)\n- [Crush vs Kimi Code CLI](https://www.anchorterminal.com/compare/crush-vs-kimi-code-cli.md)\n- [Crush vs mini-swe-agent](https://www.anchorterminal.com/compare/crush-vs-mini-swe-agent.md)\n- [Crush vs Mistral Vibe CLI](https://www.anchorterminal.com/compare/crush-vs-mistral-vibe-cli.md)\n- [Crush vs Muse Code](https://www.anchorterminal.com/compare/crush-vs-muse-code.md)\n- [Crush vs OpenAI Codex](https://www.anchorterminal.com/compare/crush-vs-openai-codex.md)\n- [Crush vs OpenCode](https://www.anchorterminal.com/compare/crush-vs-opencode.md)\n- [Crush vs OpenHands](https://www.anchorterminal.com/compare/crush-vs-openhands.md)\n- [Crush vs Prime Agent](https://www.anchorterminal.com/compare/crush-vs-prime-agent.md)\n- [Crush vs Qoder CLI](https://www.anchorterminal.com/compare/crush-vs-qoder-cli.md)\n- [Crush vs Qwen Code](https://www.anchorterminal.com/compare/crush-vs-qwen-code.md)\n- [Crush vs Mirror CLI](https://www.anchorterminal.com/compare/crush-vs-reflection-mirror.md)\n- [Crush vs Rovo Dev CLI](https://www.anchorterminal.com/compare/crush-vs-rovo-dev-cli.md)\n- [Crush vs Warp (Warp Agent CLI and the Oz Agent API)](https://www.anchorterminal.com/compare/crush-vs-warp.md)\n- [Cursor CLI vs Kiro CLI](https://www.anchorterminal.com/compare/cursor-cli-vs-kiro-cli.md)\n- [DeepSeek Harness (dsh) vs Kiro CLI](https://www.anchorterminal.com/compare/deepseek-harness-vs-kiro-cli.md)\n- [Devin vs Kiro CLI](https://www.anchorterminal.com/compare/devin-vs-kiro-cli.md)\n- [Droid CLI vs Kiro CLI](https://www.anchorterminal.com/compare/droid-cli-vs-kiro-cli.md)\n- [Pi vs Kiro CLI](https://www.anchorterminal.com/compare/earendil-pi-vs-kiro-cli.md)\n- [Gemini CLI vs Kiro CLI](https://www.anchorterminal.com/compare/gemini-cli-vs-kiro-cli.md)\n- [GitHub Copilot CLI vs Kiro CLI](https://www.anchorterminal.com/compare/github-copilot-cli-vs-kiro-cli.md)\n- [goose vs Kiro CLI](https://www.anchorterminal.com/compare/goose-vs-kiro-cli.md)\n- [Harness² vs Kiro CLI](https://www.anchorterminal.com/compare/harness2-vs-kiro-cli.md)\n- [HarnessRouter vs Kiro CLI](https://www.anchorterminal.com/compare/harnessrouter-vs-kiro-cli.md)\n- [Jules vs Kiro CLI](https://www.anchorterminal.com/compare/jules-vs-kiro-cli.md)\n- [Junie CLI vs Kiro CLI](https://www.anchorterminal.com/compare/junie-vs-kiro-cli.md)\n- [Kilo Code CLI vs Kiro CLI](https://www.anchorterminal.com/compare/kilo-code-cli-vs-kiro-cli.md)\n- [Kimi Code CLI vs Kiro CLI](https://www.anchorterminal.com/compare/kimi-code-cli-vs-kiro-cli.md)\n- [Kiro CLI vs mini-swe-agent](https://www.anchorterminal.com/compare/kiro-cli-vs-mini-swe-agent.md)\n- [Kiro CLI vs Mistral Vibe CLI](https://www.anchorterminal.com/compare/kiro-cli-vs-mistral-vibe-cli.md)\n- [Kiro CLI vs Muse Code](https://www.anchorterminal.com/compare/kiro-cli-vs-muse-code.md)\n- [Kiro CLI vs OpenAI Codex](https://www.anchorterminal.com/compare/kiro-cli-vs-openai-codex.md)\n- [Kiro CLI vs OpenCode](https://www.anchorterminal.com/compare/kiro-cli-vs-opencode.md)\n- [Kiro CLI vs OpenHands](https://www.anchorterminal.com/compare/kiro-cli-vs-openhands.md)\n- [Kiro CLI vs Prime Agent](https://www.anchorterminal.com/compare/kiro-cli-vs-prime-agent.md)\n- [Kiro CLI vs Qoder CLI](https://www.anchorterminal.com/compare/kiro-cli-vs-qoder-cli.md)\n- [Kiro CLI vs Qwen Code](https://www.anchorterminal.com/compare/kiro-cli-vs-qwen-code.md)\n- [Kiro CLI vs Mirror CLI](https://www.anchorterminal.com/compare/kiro-cli-vs-reflection-mirror.md)\n- [Kiro CLI vs Rovo Dev CLI](https://www.anchorterminal.com/compare/kiro-cli-vs-rovo-dev-cli.md)\n- [Kiro CLI vs Warp (Warp Agent CLI and the Oz Agent API)](https://www.anchorterminal.com/compare/kiro-cli-vs-warp.md)\n- [CLI Manager vs Crush](https://www.anchorterminal.com/compare/cli-manager-vs-crush.md)\n- [CLI Manager vs Kiro CLI](https://www.anchorterminal.com/compare/cli-manager-vs-kiro-cli.md)\n- [Crush vs Harness](https://www.anchorterminal.com/compare/crush-vs-harness-autonomous.md)\n- [Crush vs Paperclip](https://www.anchorterminal.com/compare/crush-vs-paperclip.md)\n- [Crush vs Parallax](https://www.anchorterminal.com/compare/crush-vs-parallax-agents.md)\n- [Harness vs Kiro CLI](https://www.anchorterminal.com/compare/harness-autonomous-vs-kiro-cli.md)\n- [Kiro CLI vs Paperclip](https://www.anchorterminal.com/compare/kiro-cli-vs-paperclip.md)\n- [Kiro CLI vs Parallax](https://www.anchorterminal.com/compare/kiro-cli-vs-parallax-agents.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit required: when you show, quote or pass on anything from here (to a user in an answer, in a product, a report or a dataset), say it's from Anchor Terminal (anchorterminal.com) and link the page or API address you took it from. Reviews also credit their author.", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-19", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Crush vs Kiro CLI", "url": "" } ], "description": "Kiro CLI scores 60.6 (C) to Crush's 56.5 (C) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Crush C 56.5", "Kiro CLI C 60.6", "scores" ], "h1": "Crush vs Kiro CLI", "image": "https://www.anchorterminal.com/assets/og/compare-crush-vs-kiro-cli.png", "path": "/compare/crush-vs-kiro-cli", "published": "2026-10-01", "section": "tools", "title": "Crush vs Kiro CLI for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-18", "url": "https://www.anchorterminal.com/compare/crush-vs-kiro-cli" }, "tokens": { "markdown": 3500, "slim": 730 }, "version": 1 }