{ "data": { "a": { "slug": "agent-zero", "name": "Agent Zero", "vendor": "Agent Zero, s.r.o.", "vendorUrl": "https://www.agent-zero.ai", "kind": "harness", "category": "agent-harnesses", "summary": "Agent Zero is an open-source agent framework that runs in a Docker container with a Linux desktop, a browser, a task scheduler and memory. Its owner reaches it through a web interface, Telegram, WhatsApp or email.", "url": "https://www.anchorterminal.com/tools/agent-zero", "markdownUrl": "https://www.anchorterminal.com/tools/agent-zero.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/agent-zero.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/agent-zero.json", "repo": "https://github.com/agent0ai/agent-zero", "license": "MIT", "transports": [], "packages": [ { "registry": "oci", "name": "agent0ai/agent-zero" } ], "auth": "none", "authNotes": "No account. The web interface has no login until the owner sets a username and password in Settings or as `AUTH_LOGIN` and `AUTH_PASSWORD`, which are stored in `/a0/usr/.env` (https://github.com/agent0ai/agent-zero/blob/main/docs/setup/vps-deployment.md). The external API takes an `X-API-KEY` header, and the optional MCP server and A2A endpoint carry the same token in the URL path. The token is derived from the instance id and the login, so it changes when either changes (https://github.com/agent0ai/agent-zero/blob/main/docs/guides/a2a-setup.md). Model access uses provider API keys or OAuth sign-in to ChatGPT (Codex), GitHub Copilot, Google Cloud Gemini or xAI (https://github.com/agent0ai/agent-zero/blob/main/plugins/_oauth/README.md).", "pricing": "free", "pricingNotes": "Free under MIT, with nothing to buy for the software. The owner pays the model provider they configure, or nothing with a local model. A beta LLM API on the vendor's site gives a daily quota to people who stake its A0T token and is separate from the software (checked 2026-10-12).", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs or the source (checked 2026-10-12).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 19429, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-12" }, "docsUrl": "https://github.com/agent0ai/agent-zero/tree/main/docs", "llmsTxt": "https://www.agent-zero.ai/llms.txt", "capabilities": [ "agent.harness", "agent.mcp-client" ], "tags": [ "open-source", "self-hosted", "local", "free", "python", "mit", "llms-txt", "docker" ], "lastRelease": "2026-09-23", "graded": true, "anchor": { "graded": true, "score": 54.2, "grade": "C", "agentReady": false, "rank": 709, "ranked": true, "rankOf": 986, "categoryRank": 19, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 62, "maintenance": 75, "payments": 60, "reliability": 57, "schema": 64, "security": 54, "transparency": 55 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-12" }, "negative": -6, "negativeNotes": [ "2026-03-17. CVE-2026-4307 (path traversal in `get_abs_path`, CVSS 4.3) and CVE-2026-4308 (server-side request forgery in document queries, CVSS 6.3), both against 0.9.7, with public exploits. The NVD entries say the vendor was contacted and did not respond. The v2.9 notes of 12 August 2026 list a fix for an SSRF regression under CVE-2026-4308. Whether CVE-2026-4307 is fixed was not established. -2. https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-4308", "2026-05-27. CVE-2026-47119, stored cross-site scripting through SVG files served by the `image_get` endpoint, CVSS 6.1, in versions before 1.15. The report (#1609) was closed as completed on 12 May 2026. Fixed, and no GitHub advisory was published. -1. https://github.com/agent0ai/agent-zero/issues/1609", "2026-09-30. CVE-2026-51852 and CVE-2026-51853, directory traversal in the file browser of versions 1.7 to 1.10, CVSS 7.5 each. Reported as issues #1539 and #1540 on 20 April 2026 and closed as completed on 24 July 2026. The file browser still starts at the container root by design. -1. https://github.com/agent0ai/agent-zero/issues/1540", "2026-09-09. Two flaws recorded in the project's own security-review ledger and fixed in v2.12 the same day. An unauthenticated Telegram webhook accepted forged updates, and WhatsApp document names could overwrite files outside the media cache before the sender check ran. The ledger rates both high. Named in the release notes, with no advisory. -2. https://github.com/agent0ai/agent-zero/blob/main/security-review/LEDGER.md" ], "verdict": "Self-hosted under the MIT licence, with nine releases in the 90 days to 12 October 2026 and breaking changes listed in the release notes. The agent runs shell commands in its container with no approval step, the web interface has no login by default, and five CVEs from the past year have no published GitHub advisory.", "bestFor": "A technical owner who wants an agent with its own Linux machine, reachable from Telegram, WhatsApp or email, with scheduled tasks and editable memory.", "strengths": [ "MIT licence, with prompts, tools, plugins and settings readable and editable in one public repository", "Nine tagged releases between 17 July and 23 September 2026, and Breaking Changes sections in the v2.11, v2.12 and v2.13 notes", "Memory dashboard to search, edit, delete and bulk-delete entries, with memory kept apart for each project by default", "No usage telemetry found in the source. The one call home is an update check that a setting turns off", "Tool Access policy can allow or block each built-in and MCP tool for a project or an agent profile" ], "weaknesses": [ "No approval step before shell commands, file changes or outgoing messages. Tool Access defaults to allow", "The web interface has no login until the owner sets a username, and the README command publishes port 80", "Five CVEs published between 17 March and 30 September 2026, none as a GitHub advisory, and no SECURITY.md or security.txt", "Infection Check, the prompt-injection audit before tool calls, ships turned off", "Empty allow-lists in the Telegram, WhatsApp and email integrations accept messages from anyone", "No public CI runs the 191 test files. The only workflows publish Docker images and close inactive issues" ], "agentNotes": [ "Set a UI login and password in Settings before publishing the port or opening a tunnel. The default has none", "Fill `allowed_users`, `allowed_numbers` or `sender_whitelist` before enabling a channel. An empty list accepts every sender", "Enable the Infection Check plugin when the agent reads mail, web pages or MCP results. It ships disabled", "Run v2.12 or later. It fixes a Telegram webhook authentication bypass and a WhatsApp media path traversal", "Call `POST /api_message` with the `X-API-KEY` header. The token changes when the UI login or password changes" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 54.2 } ], "editorialScores": { "ergonomics": 62, "maintenance": 75, "payments": 60, "reliability": 57, "schema": 64, "security": 54, "transparency": 56 }, "provenanceScore": 53 }, "connect": { "install": "docker run -p 80:80 -v a0_usr:/a0/usr agent0ai/agent-zero # or: curl -fsSL https://bash.agent-zero.ai | bash" }, "letme": { "capability": "https://letme.dev/agent.harness", "tool": "https://letme.dev/agent-zero" }, "area": "frameworks", "provenance": { "legalEntity": "Agent Zero, s.r.o.", "domain": "agent-zero.ai", "domainRegistered": "", "endpointOnVendorDomain": null, "terms": "", "privacy": "", "statusPage": "", "changelog": "https://github.com/agent0ai/agent-zero/releases", "securityTxt": "none", "checked": "2026-10-12", "notes": [ "The site footer names Agent Zero, s.r.o., ID no. 231 46 508, Nové sady 988/2, 602 00 Brno, Czech Republic, and the `LICENSE` file carries the same company's copyright.", "No terms or privacy policy for the software was found. The site's terms page covers its community platform and its cookie page covers the website, so neither is linked here and the MIT licence stands in.", "`/.well-known/security.txt` on www.agent-zero.ai answered 404 on 12 October 2026, and the repository has no SECURITY.md.", "robots.txt on www.agent-zero.ai answered 404, read as no rules. agent-zero.ai redirects to www.agent-zero.ai.", "There is no hosted endpoint. An instance answers on its owner's own host.", "The domain's registration date was not looked up." ], "score": 53 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/agent-zero.json" }, "answer": "Kiro CLI scores 59.9 (C) on agent readiness against Agent Zero's 54.2 (C), and leads in 4 of 7 scored categories. Agent Zero leads on payments \u0026 pricing.", "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-05", "graded": true, "anchor": { "graded": true, "score": 59.9, "grade": "C", "agentReady": false, "rank": 549, "ranked": true, "rankOf": 986, "categoryRank": 12, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 67, "maintenance": 73, "payments": 40, "reliability": 57, "schema": 79, "security": 66, "transparency": 67 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "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", "Eleven minor releases between 26 August and 5 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", "No local sandbox in the CLI, and AWS says its managed permission policies are client-enforced and can be circumvented", "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", "Export variables in the shell before starting. Since 2.24.0 a project `.env` file is no longer loaded into sessions, MCP servers or tools" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 59.9 } ], "editorialScores": { "ergonomics": 67, "maintenance": 73, "payments": 40, "reliability": 57, "schema": 79, "security": 66, "transparency": 62 }, "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-08", "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 answers 404. aws.amazon.com publishes a security.txt whose Expires line reads 24 September 2026, which had passed when we read it.", "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": 4360, "securityTxt": { "url": "https://kiro.dev/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-12T15:44:16.01955223Z" }, "llmsTxt": { "url": "https://kiro.dev/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-12T14:09:22.394506534Z" }, "domain": { "domain": "kiro.dev", "registered": "2019-03-01", "source": "https://pubapi.registry.google/rdap/domain/kiro.dev", "checkedAt": "2026-10-11T13:27:00.255442293Z" }, "pages": [ { "url": "https://kiro.dev/changelog/cli/", "kind": "deprecations", "status": 304, "checkedAt": "2026-10-11T19:29:12.003991548Z", "changedAt": "2026-10-10T19:04:59.979952604Z", "fingerprint": "4412f6934cee" } ], "updatedAt": "2026-10-12T15:44:16.01955223Z" } }, "facts": [ { "a": "Agent harness", "b": "Agent harness", "name": "Kind" }, { "a": "Agent Zero, s.r.o.", "b": "Amazon Web Services", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "", "b": "", "name": "Transports" }, { "a": "None", "b": "OAuth or key", "name": "Auth" }, { "a": "Free", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT", "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": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-23", "b": "2026-10-05", "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": "19k stars", "b": "4.4k stars", "name": "Popularity" } ], "faq": [ { "answer": "Kiro CLI scores 59.9 (C) on agent readiness against Agent Zero's 54.2 (C), and leads in 4 of 7 scored categories. Agent Zero leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Agent Zero or Kiro CLI?" }, { "answer": "Agent Zero is open source (MIT). No open-source release is listed for Kiro CLI.", "question": "Are Agent Zero and Kiro CLI open source?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 60 against 40" ], "also": [ "No key needed to call it", "Open source" ], "goodFor": "A technical owner who wants an agent with its own Linux machine, reachable from Telegram, WhatsApp or email, with scheduled tasks and editable memory.", "slug": "agent-zero", "watchFor": "No approval step before shell commands, file changes or outgoing messages. Tool Access defaults to allow" }, { "aheadOn": [ "Schema \u0026 documentation, 79 against 64", "Agent ergonomics, 67 against 62", "Security \u0026 auth, 66 against 54", "Transparency \u0026 trust, 67 against 55" ], "also": [ "Free to start without a card" ], "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-aider.json", "title": "Agent Zero vs Aider", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-aider" }, { "json": "https://www.anchorterminal.com/compare/agent-zero-vs-amp.json", "title": "Agent Zero vs Amp", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-amp" }, { "json": "https://www.anchorterminal.com/compare/agent-zero-vs-antigravity-cli.json", "title": "Agent Zero vs Antigravity CLI", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-antigravity-cli" }, { "json": "https://www.anchorterminal.com/compare/agent-zero-vs-claude-code.json", "title": "Agent Zero vs Claude Code", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-claude-code" }, { "json": "https://www.anchorterminal.com/compare/agent-zero-vs-cline.json", "title": "Agent Zero vs Cline", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-cline" }, { "json": "https://www.anchorterminal.com/compare/agent-zero-vs-cursor-cli.json", "title": "Agent Zero vs Cursor CLI", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-cursor-cli" }, { "json": "https://www.anchorterminal.com/compare/agent-zero-vs-devin.json", "title": "Agent Zero vs Devin", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-devin" }, { "json": "https://www.anchorterminal.com/compare/agent-zero-vs-droid-cli.json", "title": "Agent Zero vs Droid CLI", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-droid-cli" }, { "json": "https://www.anchorterminal.com/compare/agent-zero-vs-earendil-pi.json", "title": "Agent Zero vs Pi", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-earendil-pi" }, { "json": "https://www.anchorterminal.com/compare/agent-zero-vs-gemini-cli.json", "title": "Agent Zero vs Gemini CLI", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-gemini-cli" }, { "json": "https://www.anchorterminal.com/compare/agent-zero-vs-github-copilot-cli.json", "title": "Agent Zero vs GitHub Copilot CLI", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-github-copilot-cli" }, { "json": "https://www.anchorterminal.com/compare/agent-zero-vs-goose.json", "title": "Agent Zero vs goose", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-goose" }, { "json": "https://www.anchorterminal.com/compare/agent-zero-vs-kilo-code-cli.json", "title": "Agent Zero vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/agent-zero-vs-openai-codex.json", "title": "Agent Zero vs OpenAI Codex", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-openai-codex" }, { "json": "https://www.anchorterminal.com/compare/agent-zero-vs-opencode.json", "title": "Agent Zero vs OpenCode", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-opencode" }, { "json": "https://www.anchorterminal.com/compare/agent-zero-vs-openhands.json", "title": "Agent Zero vs OpenHands", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-openhands" }, { "json": "https://www.anchorterminal.com/compare/agent-zero-vs-prime-agent.json", "title": "Agent Zero vs Prime Agent", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-prime-agent" }, { "json": "https://www.anchorterminal.com/compare/agent-zero-vs-qwen-code.json", "title": "Agent Zero vs Qwen Code", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-qwen-code" }, { "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-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-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/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-kiro-cli.json", "title": "Cline vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/cline-vs-kiro-cli" }, { "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/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/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/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-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-paperclip.json", "title": "Kiro CLI vs Paperclip", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-paperclip" } ], "scores": [ { "agent-zero": 57, "by": 0, "edge": "", "key": "reliability", "kiro-cli": 57, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "agent-zero": 64, "by": 15, "edge": "kiro-cli", "key": "schema", "kiro-cli": 79, "name": "Schema \u0026 documentation", "weight": 13 }, { "agent-zero": 62, "by": 5, "edge": "kiro-cli", "key": "ergonomics", "kiro-cli": 67, "name": "Agent ergonomics", "weight": 13 }, { "agent-zero": 54, "by": 12, "edge": "kiro-cli", "key": "security", "kiro-cli": 66, "name": "Security \u0026 auth", "weight": 14 }, { "agent-zero": 60, "by": 20, "edge": "agent-zero", "key": "payments", "kiro-cli": 40, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "agent-zero": 75, "by": 2, "edge": "agent-zero", "key": "maintenance", "kiro-cli": 73, "name": "Maintenance \u0026 community", "weight": 7 }, { "agent-zero": 55, "by": 12, "edge": "kiro-cli", "key": "transparency", "kiro-cli": 67, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Kiro CLI scores 59.9 (C) on agent readiness against Agent Zero's 54.2 (C), and leads in 4 of 7 scored categories. Agent Zero leads on payments \u0026 pricing. Both do agent harnesses.", "verdicts": { "agent-zero": "Self-hosted under the MIT licence, with nine releases in the 90 days to 12 October 2026 and breaking changes listed in the release notes. The agent runs shell commands in its container with no approval step, the web interface has no login by default, and five CVEs from the past year have no published GitHub advisory.", "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/agent-zero-vs-kiro-cli", "json": "https://www.anchorterminal.com/compare/agent-zero-vs-kiro-cli.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/agent-zero-vs-kiro-cli.md", "slim": "https://www.anchorterminal.com/compare/agent-zero-vs-kiro-cli.min.md" }, "markdown": "Kiro CLI scores 59.9 (C) on agent readiness against Agent Zero's 54.2 (C), and leads in 4 of 7 scored categories. Agent Zero leads on payments \u0026 pricing. Both do agent harnesses.\n\n- Agent Zero: grade C, 54.2/100, rank #709 of 986. Markdown https://www.anchorterminal.com/tools/agent-zero.md · JSON https://www.anchorterminal.com/api/v1/tools/agent-zero.json\n- Kiro CLI: grade C, 59.9/100, rank #549 of 986. 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 205 harnesses comparisons: https://www.anchorterminal.com/compare/agent-harnesses/index.md\n\n## Which one, for what\n\n### Agent Zero (C)\n\nGood for: A technical owner who wants an agent with its own Linux machine, reachable from Telegram, WhatsApp or email, with scheduled tasks and editable memory.\n\nAhead on:\n- Payments \u0026 pricing, 60 against 40\n\nAlso in its favour:\n- No key needed to call it\n- Open source\n\nWatch for: No approval step before shell commands, file changes or outgoing messages. Tool Access defaults to allow\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 64\n- Agent ergonomics, 67 against 62\n- Security \u0026 auth, 66 against 54\n- Transparency \u0026 trust, 67 against 55\n\nAlso in its favour:\n- Free to start without a card\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 | Agent Zero | Kiro CLI | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 57 | 57 | even |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 64 | 79 | Kiro CLI +15 |\n| Agent ergonomics | 13% (16.2 this run) | 62 | 67 | Kiro CLI +5 |\n| Security \u0026 auth | 14% (17.5 this run) | 54 | 66 | Kiro CLI +12 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 40 | Agent Zero +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 75 | 73 | Agent Zero +2 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 55 | 67 | Kiro CLI +12 |\n| Negative events | ≤15 | -6 | -4 | |\n| **Total** | | **54.2 · C** | **59.9 · C** | |\n\n## Facts side by side\n\n| Fact | Agent Zero | Kiro CLI |\n| --- | --- | --- |\n| Kind | Agent harness | Agent harness |\n| Vendor | Agent Zero, s.r.o. | Amazon Web Services |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | | |\n| Auth | None | OAuth or key |\n| Pricing | Free | Freemium |\n| x402 | no | no |\n| Licence | MIT | 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 | yes | yes |\n| Last release | 2026-09-23 | 2026-10-05 |\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 | 19k stars | 4.4k stars |\n\n## Verdicts\n\n**Agent Zero.** Self-hosted under the MIT licence, with nine releases in the 90 days to 12 October 2026 and breaking changes listed in the release notes. The agent runs shell commands in its container with no approval step, the web interface has no login by default, and five CVEs from the past year have no published GitHub advisory.\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### Agent Zero\n\n1. Set a UI login and password in Settings before publishing the port or opening a tunnel. The default has none\n2. Fill `allowed_users`, `allowed_numbers` or `sender_whitelist` before enabling a channel. An empty list accepts every sender\n3. Enable the Infection Check plugin when the agent reads mail, web pages or MCP results. It ships disabled\n4. Run v2.12 or later. It fixes a Telegram webhook authentication bypass and a WhatsApp media path traversal\n5. Call `POST /api_message` with the `X-API-KEY` header. The token changes when the UI login or password changes\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. Export variables in the shell before starting. Since 2.24.0 a project `.env` file is no longer loaded into sessions, MCP servers or tools\n\n## Questions\n\n### Which is better for AI agents, Agent Zero or Kiro CLI?\n\nKiro CLI scores 59.9 (C) on agent readiness against Agent Zero's 54.2 (C), and leads in 4 of 7 scored categories. Agent Zero leads on payments \u0026 pricing.\n\n### Are Agent Zero and Kiro CLI open source?\n\nAgent Zero is open source (MIT). No open-source release is listed for Kiro CLI.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/agent-zero-vs-kiro-cli.json, and with the fewest tokens: https://www.anchorterminal.com/compare/agent-zero-vs-kiro-cli.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"agent-zero\", \"b\": \"kiro-cli\"}`. From a terminal: `anchor compare agent-zero kiro-cli`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/agent-zero.json and https://www.anchorterminal.com/api/v1/tools/kiro-cli.json\n\n## Other comparisons with Agent Zero or Kiro CLI\n\n- [Agent Zero vs Aider](https://www.anchorterminal.com/compare/agent-zero-vs-aider.md)\n- [Agent Zero vs Amp](https://www.anchorterminal.com/compare/agent-zero-vs-amp.md)\n- [Agent Zero vs Antigravity CLI](https://www.anchorterminal.com/compare/agent-zero-vs-antigravity-cli.md)\n- [Agent Zero vs Claude Code](https://www.anchorterminal.com/compare/agent-zero-vs-claude-code.md)\n- [Agent Zero vs Cline](https://www.anchorterminal.com/compare/agent-zero-vs-cline.md)\n- [Agent Zero vs Cursor CLI](https://www.anchorterminal.com/compare/agent-zero-vs-cursor-cli.md)\n- [Agent Zero vs Devin](https://www.anchorterminal.com/compare/agent-zero-vs-devin.md)\n- [Agent Zero vs Droid CLI](https://www.anchorterminal.com/compare/agent-zero-vs-droid-cli.md)\n- [Agent Zero vs Pi](https://www.anchorterminal.com/compare/agent-zero-vs-earendil-pi.md)\n- [Agent Zero vs Gemini CLI](https://www.anchorterminal.com/compare/agent-zero-vs-gemini-cli.md)\n- [Agent Zero vs GitHub Copilot CLI](https://www.anchorterminal.com/compare/agent-zero-vs-github-copilot-cli.md)\n- [Agent Zero vs goose](https://www.anchorterminal.com/compare/agent-zero-vs-goose.md)\n- [Agent Zero vs Kilo Code CLI](https://www.anchorterminal.com/compare/agent-zero-vs-kilo-code-cli.md)\n- [Agent Zero vs OpenAI Codex](https://www.anchorterminal.com/compare/agent-zero-vs-openai-codex.md)\n- [Agent Zero vs OpenCode](https://www.anchorterminal.com/compare/agent-zero-vs-opencode.md)\n- [Agent Zero vs OpenHands](https://www.anchorterminal.com/compare/agent-zero-vs-openhands.md)\n- [Agent Zero vs Prime Agent](https://www.anchorterminal.com/compare/agent-zero-vs-prime-agent.md)\n- [Agent Zero vs Qwen Code](https://www.anchorterminal.com/compare/agent-zero-vs-qwen-code.md)\n- [Aider vs Kiro CLI](https://www.anchorterminal.com/compare/aider-vs-kiro-cli.md)\n- [Amp vs Kiro CLI](https://www.anchorterminal.com/compare/amp-vs-kiro-cli.md)\n- [Antigravity CLI vs Kiro CLI](https://www.anchorterminal.com/compare/antigravity-cli-vs-kiro-cli.md)\n- [Claude Code vs Kiro CLI](https://www.anchorterminal.com/compare/claude-code-vs-kiro-cli.md)\n- [Cline vs Kiro CLI](https://www.anchorterminal.com/compare/cline-vs-kiro-cli.md)\n- [Cursor CLI vs Kiro CLI](https://www.anchorterminal.com/compare/cursor-cli-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- [Kilo Code CLI vs Kiro CLI](https://www.anchorterminal.com/compare/kilo-code-cli-vs-kiro-cli.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 Qwen Code](https://www.anchorterminal.com/compare/kiro-cli-vs-qwen-code.md)\n- [Kiro CLI vs Paperclip](https://www.anchorterminal.com/compare/kiro-cli-vs-paperclip.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-12", "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" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Agent Zero vs Kiro CLI", "url": "" } ], "description": "Kiro CLI scores 59.9 (C) to Agent Zero's 54.2 (C) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Agent Zero C 54.2", "Kiro CLI C 59.9", "scores" ], "h1": "Agent Zero vs Kiro CLI", "image": "https://www.anchorterminal.com/assets/og/compare-agent-zero-vs-kiro-cli.png", "path": "/compare/agent-zero-vs-kiro-cli", "published": "2026-10-01", "section": "tools", "title": "Agent Zero vs Kiro CLI for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-12", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-kiro-cli" }, "tokens": { "markdown": 2700, "slim": 680 }, "version": 1 }