{ "data": { "a": { "slug": "clawboo", "name": "Clawboo", "vendor": "Sanreds", "vendorUrl": "https://www.claw.boo", "kind": "harness", "category": "agent-harnesses", "summary": "Clawboo is an open-source, self-hosted dashboard and server that runs a team of AI agents on one task board. A lead agent, Boo Zero, hands tasks to Claude Code, Codex, Hermes, OpenClaw or Clawboo's own built-in agents.", "url": "https://www.anchorterminal.com/tools/clawboo", "markdownUrl": "https://www.anchorterminal.com/tools/clawboo.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/clawboo.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/clawboo.json", "dns": "clawboo.grade.anchorterminal.com", "repo": "https://github.com/clawboo/clawboo", "license": "MIT", "transports": [], "packages": [ { "registry": "npm", "name": "clawboo" } ], "auth": "none", "authNotes": "No Clawboo account. On the default loopback bind the API needs no credential. An optional shared token, `STUDIO_ACCESS_TOKEN`, puts every `/api/` route behind a `clawboo_access` cookie, with no users, roles or per-person revocation. Agents Clawboo starts reach its MCP servers through signed attach URLs.", "pricing": "free", "pricingNotes": "Free and MIT, self-hosted, with nothing to buy. The owner pays the model providers or plans each runtime uses, or runs a local Ollama model with no key. No hosted option is offered.", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the documentation (llms-full.txt), the README or the npm package metadata (checked 2026-11-01).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 100, "pypiWeekly": null, "asOf": "2026-11-01" }, "docsUrl": "https://docs.claw.boo", "llmsTxt": "https://docs.claw.boo/llms.txt", "capabilities": [ "agent.multi-agent", "agent.mcp-client" ], "tags": [ "open-source", "self-hosted", "local", "free", "no-card", "llms-txt", "mcp", "typescript" ], "lastRelease": "2026-10-21", "graded": true, "anchor": { "graded": true, "score": 61.4, "grade": "C", "agentReady": false, "rank": 555, "ranked": true, "rankOf": 1251, "categoryRank": 15, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 75, "maintenance": 51, "payments": 60, "reliability": 52, "schema": 83, "security": 70, "transparency": 58 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": -4, "negativeNotes": [ "Undated advisory on the security page, read 1 November 2026. On 0.5.0 (21 October 2026) and older, any request from 127.0.0.1 reaches `/api/mcp/` without the access cookie, so a reverse proxy on the same machine exposes the boards, memory, team chat, tools and signed attach URLs for any agent, even with `STUDIO_ACCESS_TOKEN` set. Published by the maintainer with a proxy rule to block it, fixed on main and not released, in a setup that isn't the default, -3. https://docs.claw.boo/operating/security", "Listed under Unreleased in the changelog, read 1 November 2026. On 0.5.0 and older, an access token containing a character outside letters, digits and `.`, `_`, `~`, `-` turned the access check off while the server kept running, leaving a proxied dashboard open. Fixed on main and not released, -1. https://docs.claw.boo/appendices/changelog" ], "verdict": "Tasks, memory, team chat and connectors are shared across five runtimes through four MCP servers, with documentation that states each default and limit. Claude Code, Codex and Hermes run with their sandboxes and approval prompts off and no setting to change it, and a reverse-proxy exposure of the MCP servers is fixed only on the unreleased main branch.", "bestFor": "One person on one computer who wants several coding and general agents on one board, with shared memory and a lead agent that routes work.", "strengths": [ "One board, one team chat and one shared memory across Clawboo Native, Claude Code, Codex, Hermes and OpenClaw agents", "No telemetry per the docs, which list the three requests the server makes itself and the two the dashboard makes", "Loopback bind by default, a same-origin guard against browser and DNS-rebinding attacks, and a refusal to start on a network bind without a token", "About 120 documentation pages, served as Markdown with llms.txt and llms-full.txt, including a known-issues page and every built-in limit with its source line", "npm releases carry SLSA provenance from the repository's publish workflow, with CodeQL and Dependabot in the repository" ], "weaknesses": [ "Claude Code runs in `bypassPermissions`, Codex with `danger-full-access` and Hermes with `--yolo`, with no setting to change it and no sandbox", "On 0.5.0 and older, a same-machine reverse proxy exposes `/api/mcp/` without the access cookie. The fix is on main and unreleased on 1 November 2026", "No access token by default, so any local program can call the API and answer approval cards", "Keys saved under Providers are also written in plain text to `~/.openclaw/.env` and each OpenClaw agent's `auth-profiles.json`", "Version 0.5.0, with two releases in the 90 days to 1 November 2026 and budgets that only warn unless set to a hard cap" ], "agentNotes": [ "Run `npx clawboo@latest`, not a bare `npx clawboo`, which can reuse an older cached build. Node.js 22.12 or newer is required", "On 0.5.0 behind nginx, Caddy or a Cloudflare Tunnel, deny `/api/mcp/` at the proxy and set `STUDIO_ACCESS_TOKEN` from `openssl rand -hex 24`", "Give Claude Code, Codex and Hermes teammates only work you would let run unattended, or run Clawboo under a separate user account or VM", "Create a hard-cap budget in Settings \u003e Insights \u003e Governance before long runs. A fresh install has no budget and new budgets only warn", "Install `@anthropic-ai/claude-agent-sdk` globally beside Clawboo for Claude Code teammates. A one-off `npx` run cannot load it" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 61.4 } ], "editorialScores": { "ergonomics": 75, "maintenance": 51, "payments": 60, "reliability": 52, "schema": 83, "security": 70, "transparency": 80 }, "provenanceScore": 36, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npx clawboo@latest # Node.js 22.12 or newer", "http": "curl http://localhost:18790/api/health", "headless": { "command": "curl -X POST http://localhost:18790/api/teams/\u003cteam-id\u003e/chat -H 'Content-Type: application/json' -d '{\"message\":\"Plan the launch checklist.\"}'" } }, "letme": { "capability": "https://letme.dev/agent.multi-agent", "tool": "https://letme.dev/clawboo" }, "area": "frameworks", "provenance": { "legalEntity": "", "domain": "claw.boo", "domainRegistered": "", "endpointOnVendorDomain": null, "terms": "", "privacy": "", "statusPage": "", "changelog": "https://docs.claw.boo/appendices/changelog", "securityTxt": "none", "checked": "2026-11-01", "notes": [ "No legal entity is named in the repository, the docs or the npm package. The MIT licence reads Copyright (c) 2026 Sanreds, and the npm package's only maintainer is sanreds.", "www.claw.boo was not read. Its robots.txt disallows Claude-Web in Cloudflare's managed block and later allows ClaudeBot and anthropic-ai, so the site's terms and privacy pages, if any, are unchecked.", "docs.claw.boo/.well-known/security.txt answered 404 on 1 November 2026. SECURITY.md sends reports to GitHub private vulnerability reporting.", "The software is self-hosted, so there is no vendor endpoint or status page to check. The domain registration date was not looked up." ], "score": 36 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/clawboo.json" }, "answer": "Clawboo and Kiro CLI score within a point of each other on agent readiness, 61.4 (C) and 60.8 (C). Kiro CLI leads on reliability, maintenance \u0026 community and transparency \u0026 trust.", "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", "dns": "kiro-cli.grade.anchorterminal.com", "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.8, "grade": "C", "agentReady": false, "rank": 581, "ranked": true, "rankOf": 1251, "categoryRank": 17, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 67, "maintenance": 73, "payments": 40, "reliability": 57, "schema": 79, "security": 69, "transparency": 71 }, "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.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 60.8 } ], "editorialScores": { "ergonomics": 67, "maintenance": 73, "payments": 40, "reliability": 57, "schema": 79, "security": 69, "transparency": 66 }, "provenanceScore": 76, "checked": { "categories": { "ergonomics": "2026-10-17", "maintenance": "2026-10-17", "payments": "2026-10-17", "reliability": "2026-10-17", "schema": "2026-10-17", "security": "2026-10-17", "transparency": "2026-10-17" }, "last": "2026-10-17", "lastMoved": "2026-10-28", "oldest": "2026-10-17", "stale": false, "staleAfterDays": 90 } }, "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": 76 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/kiro-cli.json", "live": { "slug": "kiro-cli", "githubStars": 4421, "securityTxt": { "url": "https://kiro.dev/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-31T15:41:47.111941634Z" }, "llmsTxt": { "url": "https://kiro.dev/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-31T15:11:03.706002858Z" }, "domain": { "domain": "kiro.dev", "registered": "2019-03-01", "source": "https://pubapi.registry.google/rdap/domain/kiro.dev", "checkedAt": "2026-10-25T13:53:30.938182416Z" }, "pages": [ { "url": "https://kiro.dev/changelog/cli/", "kind": "deprecations", "status": 200, "checkedAt": "2026-10-31T06:14:25.251371933Z", "changedAt": "2026-10-31T06:14:25.251371933Z", "fingerprint": "a590c4863382" }, { "url": "https://kiro.dev/changelog/models/", "kind": "deprecations", "status": 200, "checkedAt": "2026-10-31T06:14:27.388041825Z", "changedAt": "2026-10-31T06:14:27.388041825Z", "fingerprint": "adb4df2f8d03" } ], "github": { "repo": "kirodotdev/kiro", "checkedAt": "2026-10-26T07:37:58.454527374Z", "stars": 4398, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-18T11:35:32Z", "openIssues": 1595, "openPRs": 7, "issuesOpened90d": 1610, "issuesClosed90d": 2659, "prsMerged90d": 2, "ci": { "branch": "main", "runs": 1, "success": 0, "failure": 1, "other": 0, "latest": "failure", "latestAt": "2026-03-23T17:52:28Z" } }, "updatedAt": "2026-10-31T16:02:20.034719841Z" } }, "edges": [ { "by": 22, "category": "maintenance", "leads": "kiro-cli", "name": "Maintenance \u0026 community", "reasons": { "a": "0.5.0 was published to npm on 21 October 2026 (30). Two releases in the 90 days to 1 November 2026, 0.4.0 on 28 September and 0.5.0, below the three the line asks for (0). github.com was unreachable, so replies to issues, pull requests and Discussions are unchecked. The CI file cites issue #140 as fixed (3). One public npm package, current, with no entry in the official MCP registry for its four servers (10). CI, CodeQL, weekly Dependabot and SLSA provenance on 0.4.0 and 0.5.0, with `@composio/client` pinned to an alpha (8).", "b": "2.31.1 on 14 October 2026 (30). At least 12 minor versions (2.20.0 on 26 August to 2.31.0 on 13 October) and their patches (20). A public issue tracker with area labels and triage automation, 69 cli issues closed against 96 opened in the 30 days to 8 October, and a Discord server, per the 8 October check, not re-read on 17 October. We didn't establish how many replies come from staff (14). No SDK and no registry entry. The ACP server is kept current, with a migration guide for clients moving to V3 (6). Closed source, so no CI or dependency health to read. The installer verifies checksums (3). 30+20+14+6+3 = 73." }, "scores": { "a": 51, "b": 73 } }, { "by": 20, "category": "payments", "leads": "clawboo", "name": "Payments \u0026 pricing", "reasons": { "a": "No payment protocol (0). Read with the self-hosted rule. Free under MIT with nothing to buy (20). No card and no Clawboo account (20). One `npx` command installs and starts it with no sign-up (20). Model costs belong to the providers the owner connects.", "b": "Harness reading of the published rubric, scored on the Kiro subscription the CLI needs. No payment protocol (0). Plan prices, the $0.04 credit price and per-model credit multipliers are public without a login (20). Kiro Free has 50 credits a month, and the pricing page asks for a card only on upgrade (20). A person signs in through a browser or device flow, and the API key for headless runs is created by hand at app.kiro.dev on a paid plan (0)." }, "scores": { "a": 60, "b": 40 } }, { "by": 13, "category": "transparency", "leads": "kiro-cli", "name": "Transparency \u0026 trust", "reasons": { "a": "MIT, Copyright 2026 Sanreds, with a third-party notices file (30). The docs list every file Clawboo writes, which copies of keys are encrypted and which are plain text, retention for stored tool results (7 days) and pending approvals (24 hours), and that prompts go only to connected providers. There is no privacy statement, and the website wasn't read (22). The 0.1.x line is deprecated on npm with a note in the changelog, and removals are dated in release notes, with no written deprecation policy or notice period (10). No telemetry, with the server's own outbound requests disclosed, though the npm update check has no setting (18).", "b": "Proprietary, with clear terms. The licence page puts the CLI under the AWS Customer Agreement and the AWS Intellectual Property Licence, where the Amazon Q Developer CLI it replaced was Apache 2.0 (15). The data protection page says what is stored for Free, individual and enterprise users, names US East (N. Virginia) for storage, lists inference regions, and gives 60 days for Free Tier abuse detection and 30 days for some models. It agrees with sections 50.3 and 50.14 of the AWS Service Terms. No general retention period for stored content was found, per the 8 October check (22). The models page has a model lifecycle section (page updated 17 October 2026) with Experimental, Active and EOL stages, says Kiro generally schedules model end of life alongside Amazon Bedrock and shows the date in the model picker, and lists Claude Sonnet 4.0 as ending on 14 October 2026. 2.30.0 says V3 becomes the default with CLI 3.0 at the end of October, Classic sessions carry a deprecation notice, and V3 has a breaking-change table and migration guides. No minimum notice period is stated, and we found no notice of the Sonnet 4 date before the 14 October changelog entry (14). Telemetry types are listed and `telemetry.enabled` turns them off, with collection on by default (15). 15+22+14+15 = 66." }, "scores": { "a": 58, "b": 71 } }, { "by": 8, "category": "ergonomics", "leads": "clawboo", "name": "Agent ergonomics", "reasons": { "a": "Harness reading, scored on what an agent or pipeline driving it has to supply. Four MCP servers keep tool lists small (12 Tasks tools, 4 Memory tools, 2 or 3 TeamChat tools, and Tools with four demonstration builtins plus granted connectors), Clawboo Native gets a read-only Tasks subset, and Tools results over 16 KiB are trimmed with a handle to read the rest (22). Circuit breakers stop task-runner runs after more than 30 tool calls or 200,000 tokens a minute, and team chat caps hand-offs at 8 a turn and three levels. Budgets warn only unless set to a hard cap, and a hard cap stops most runs only between runs (14). REST errors use one `{error}` shape, refused MCP calls return `denied:` with a reason prefix, and 429s carry `Retry-After` (16). `claim_task` and `assign_task` are atomic, illegal status changes are refused by name, the board survives restarts and routines resume after failure. No MCP tool annotations are documented (14). One `npx` command and a provider key or a local Ollama, but Claude Code teammates need a global install with the Agent SDK, and there is no client SDK (9).", "b": "Framework reading, adapted to a harness driven by a pipeline. `--trust-tools` limits approved tools, `disabledTools` removes MCP tools per server, tool search loads MCP tools on demand, and custom agents carry their own tool set (20). Compaction and a workflow timeout (`KIRO_HEADLESS_WORKFLOW_TIMEOUT_SECS`, six hours by default) exist, but no cap on turns or run time for a plain headless run was found (10). Distinct exit codes for MCP startup failure and a missing agent, `--require-mcp-startup`, and a final interruption record in stream-json, with exit 1 for everything else (14). Sessions are saved every turn, with `--resume`, `--resume-id` and checkpoints with rewind (15). No SDK. The programmatic interfaces are the headless command and the ACP server, and a headless run needs a paid-plan API key and explicit trust flags (8)." }, "scores": { "a": 75, "b": 67 } }, { "by": 5, "category": "reliability", "leads": "kiro-cli", "name": "Reliability", "reasons": { "a": "Read as local software. The official npm package `clawboo` states Node.js 22.12 or newer, and the README says macOS, Linux and Windows are supported (20). `ci.yml` runs lint, typecheck, Vitest and a real-concurrency suite on Linux and platform suites on Windows and macOS, and `publish.yml` reruns build, lint, typecheck, tests and a clean-install boot before it publishes. 0.5.0 carries provenance from that workflow on main, so its checks passed at that commit, but run results on main couldn't be read (15). github.com was unreachable, so open crash and regression issues are unchecked. A known-issues page lists 25 entries with a status each, three of them fixed on main (5). Changesets write a changelog entry per release, and removals and the 0.2.0 database reset are called out, though breaking changes arrive in minor versions before 1.0 (12). Version 0.5.0, and SECURITY.md says pre-1.0 (0).", "b": "Local-package reading, the same as the other closed-source harnesses. An install script that verifies SHA-256 checksums, a .deb, an AppImage and a PowerShell script, with macOS, Windows 11 and Linux (glibc 2.34 or newer, or musl) stated (20). No public CI or test suite, since the source isn't published and the GitHub repository is an issue tracker (0). Per the 8 October check, not re-read on 17 October, 1,401 open issues in the shared Kiro tracker, 428 labelled cli, with 96 cli issues opened and 69 closed in the 30 days to 8 October, area labels, a triage label and stale-issue automation. Open reports from the week to 8 October included a `--no-interactive` run that never exits after a refusal (12). A dated changelog for every release and a breaking-change table with a migration guide for V3, which runs beside 2.x until the user opts in, though 2.24.0 stopped loading project `.env` files in a minor version (10). 2.31.1 is the released line, with V3 still an early release that 2.30.0 says becomes the default with CLI 3.0 at the end of October (15). 20+0+12+10+15 = 57." }, "scores": { "a": 52, "b": 57 } } ], "facts": [ { "a": "Agent harness", "b": "Agent harness", "name": "Kind" }, { "a": "Sanreds", "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-10-21", "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": "not read yet", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not read yet", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "100 npm/wk", "b": "4.4k stars", "name": "Popularity" }, { "a": "none", "b": "2.8/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "Clawboo and Kiro CLI score within a point of each other on agent readiness, 61.4 (C) and 60.8 (C). Kiro CLI leads on reliability, maintenance \u0026 community and transparency \u0026 trust.", "question": "Which is better for AI agents, Clawboo or Kiro CLI?" }, { "answer": "Clawboo is open source (MIT). No open-source release is listed for Kiro CLI.", "question": "Are Clawboo and Kiro CLI open source?" } ], "goodFor": [ { "aheadOn": [ "Agent ergonomics, 75 against 67", "Payments \u0026 pricing, 60 against 40" ], "also": [ "No key needed to call it", "Open source" ], "goodFor": "One person on one computer who wants several coding and general agents on one board, with shared memory and a lead agent that routes work.", "slug": "clawboo", "watchFor": "Claude Code runs in `bypassPermissions`, Codex with `danger-full-access` and Hermes with `--yolo`, with no setting to change it and no sandbox" }, { "aheadOn": [ "Reliability, 57 against 52", "Maintenance \u0026 community, 73 against 51", "Transparency \u0026 trust, 71 against 58" ], "also": null, "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" } ], "history": { "clawboo": null, "kiro-cli": [ { "causes": [ "evidence" ], "date": "2026-10-28", "delta": 0.1, "from": 60.7, "fromGrade": "C", "to": 60.8, "toGrade": "C" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 60.6, "fromGrade": "C", "to": 60.7, "toGrade": "C" }, { "causes": [ "security", "product" ], "date": "2026-10-17", "delta": 0.7, "from": 59.9, "fromGrade": "C", "to": 60.6, "toGrade": "C" } ] }, "job": { "capability": "agent.multi-agent", "name": "Multi-agent orchestration" }, "others": [ { "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-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/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-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/crush-vs-kiro-cli.json", "title": "Crush vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/crush-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/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/deepseek-superagent-vs-kiro-cli.json", "title": "dsh-superagent (DeepSeek) vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-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-minimax-code.json", "title": "Kiro CLI vs MiniMax Code", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-minimax-code" }, { "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-openmausbot.json", "title": "Kiro CLI vs OpenMausBot", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-openmausbot" }, { "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-unstoppable.json", "title": "Kiro CLI vs Unstoppable", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-unstoppable" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-vibe-trading.json", "title": "Kiro CLI vs Vibe-Trading", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-vibe-trading" }, { "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/amp-vs-clawboo.json", "title": "Amp vs Clawboo", "url": "https://www.anchorterminal.com/compare/amp-vs-clawboo" }, { "json": "https://www.anchorterminal.com/compare/antigravity-cli-vs-clawboo.json", "title": "Antigravity CLI vs Clawboo", "url": "https://www.anchorterminal.com/compare/antigravity-cli-vs-clawboo" }, { "json": "https://www.anchorterminal.com/compare/auggie-vs-clawboo.json", "title": "Auggie CLI vs Clawboo", "url": "https://www.anchorterminal.com/compare/auggie-vs-clawboo" }, { "json": "https://www.anchorterminal.com/compare/claude-code-vs-clawboo.json", "title": "Claude Code vs Clawboo", "url": "https://www.anchorterminal.com/compare/claude-code-vs-clawboo" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-cli-manager.json", "title": "Clawboo vs CLI Manager", "url": "https://www.anchorterminal.com/compare/clawboo-vs-cli-manager" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-cline.json", "title": "Clawboo vs Cline", "url": "https://www.anchorterminal.com/compare/clawboo-vs-cline" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-crush.json", "title": "Clawboo vs Crush", "url": "https://www.anchorterminal.com/compare/clawboo-vs-crush" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-deepseek-harness.json", "title": "Clawboo vs DeepSeek Harness (dsh)", "url": "https://www.anchorterminal.com/compare/clawboo-vs-deepseek-harness" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-deepseek-superagent.json", "title": "Clawboo vs dsh-superagent (DeepSeek)", "url": "https://www.anchorterminal.com/compare/clawboo-vs-deepseek-superagent" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-devin.json", "title": "Clawboo vs Devin", "url": "https://www.anchorterminal.com/compare/clawboo-vs-devin" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-droid-cli.json", "title": "Clawboo vs Droid CLI", "url": "https://www.anchorterminal.com/compare/clawboo-vs-droid-cli" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-gemini-cli.json", "title": "Clawboo vs Gemini CLI", "url": "https://www.anchorterminal.com/compare/clawboo-vs-gemini-cli" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-github-copilot-cli.json", "title": "Clawboo vs GitHub Copilot CLI", "url": "https://www.anchorterminal.com/compare/clawboo-vs-github-copilot-cli" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-goose.json", "title": "Clawboo vs goose", "url": "https://www.anchorterminal.com/compare/clawboo-vs-goose" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-harness-autonomous.json", "title": "Clawboo vs Harness", "url": "https://www.anchorterminal.com/compare/clawboo-vs-harness-autonomous" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-harnessrouter.json", "title": "Clawboo vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/clawboo-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-jules.json", "title": "Clawboo vs Jules", "url": "https://www.anchorterminal.com/compare/clawboo-vs-jules" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-junie.json", "title": "Clawboo vs Junie CLI", "url": "https://www.anchorterminal.com/compare/clawboo-vs-junie" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-kilo-code-cli.json", "title": "Clawboo vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/clawboo-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-kimi-code-cli.json", "title": "Clawboo vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/clawboo-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-minimax-code.json", "title": "Clawboo vs MiniMax Code", "url": "https://www.anchorterminal.com/compare/clawboo-vs-minimax-code" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-mistral-vibe-cli.json", "title": "Clawboo vs Mistral Vibe CLI", "url": "https://www.anchorterminal.com/compare/clawboo-vs-mistral-vibe-cli" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-muse-code.json", "title": "Clawboo vs Muse Code", "url": "https://www.anchorterminal.com/compare/clawboo-vs-muse-code" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-opencode.json", "title": "Clawboo vs OpenCode", "url": "https://www.anchorterminal.com/compare/clawboo-vs-opencode" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-openhands.json", "title": "Clawboo vs OpenHands", "url": "https://www.anchorterminal.com/compare/clawboo-vs-openhands" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-openmausbot.json", "title": "Clawboo vs OpenMausBot", "url": "https://www.anchorterminal.com/compare/clawboo-vs-openmausbot" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-paperclip.json", "title": "Clawboo vs Paperclip", "url": "https://www.anchorterminal.com/compare/clawboo-vs-paperclip" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-parallax-agents.json", "title": "Clawboo vs Parallax", "url": "https://www.anchorterminal.com/compare/clawboo-vs-parallax-agents" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-prime-agent.json", "title": "Clawboo vs Prime Agent", "url": "https://www.anchorterminal.com/compare/clawboo-vs-prime-agent" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-qoder-cli.json", "title": "Clawboo vs Qoder CLI", "url": "https://www.anchorterminal.com/compare/clawboo-vs-qoder-cli" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-qwen-code.json", "title": "Clawboo vs Qwen Code", "url": "https://www.anchorterminal.com/compare/clawboo-vs-qwen-code" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-reflection-mirror.json", "title": "Clawboo vs Mirror CLI", "url": "https://www.anchorterminal.com/compare/clawboo-vs-reflection-mirror" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-rovo-dev-cli.json", "title": "Clawboo vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/clawboo-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-unstoppable.json", "title": "Clawboo vs Unstoppable", "url": "https://www.anchorterminal.com/compare/clawboo-vs-unstoppable" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-vibe-trading.json", "title": "Clawboo vs Vibe-Trading", "url": "https://www.anchorterminal.com/compare/clawboo-vs-vibe-trading" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-warp.json", "title": "Clawboo vs Warp (Warp Agent CLI and the Oz Agent API)", "url": "https://www.anchorterminal.com/compare/clawboo-vs-warp" }, { "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/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" } ], "panel": null, "scores": [ { "by": 5, "clawboo": 52, "edge": "kiro-cli", "key": "reliability", "kiro-cli": 57, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 4, "clawboo": 83, "edge": "clawboo", "key": "schema", "kiro-cli": 79, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 8, "clawboo": 75, "edge": "clawboo", "key": "ergonomics", "kiro-cli": 67, "name": "Agent ergonomics", "weight": 13 }, { "by": 1, "clawboo": 70, "edge": "clawboo", "key": "security", "kiro-cli": 69, "name": "Security \u0026 auth", "weight": 14 }, { "by": 20, "clawboo": 60, "edge": "clawboo", "key": "payments", "kiro-cli": 40, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 22, "clawboo": 51, "edge": "kiro-cli", "key": "maintenance", "kiro-cli": 73, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 13, "clawboo": 58, "edge": "kiro-cli", "key": "transparency", "kiro-cli": 71, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Clawboo and Kiro CLI score within a point of each other on agent readiness, 61.4 (C) and 60.8 (C). Kiro CLI leads on reliability, maintenance \u0026 community and transparency \u0026 trust. Both do multi-agent orchestration.", "tasks": null, "tutorials": [], "verdicts": { "clawboo": "Tasks, memory, team chat and connectors are shared across five runtimes through four MCP servers, with documentation that states each default and limit. Claude Code, Codex and Hermes run with their sandboxes and approval prompts off and no setting to change it, and a reverse-proxy exposure of the MCP servers is fixed only on the unreleased main branch.", "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/clawboo-vs-kiro-cli", "json": "https://www.anchorterminal.com/compare/clawboo-vs-kiro-cli.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/clawboo-vs-kiro-cli.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/clawboo-vs-kiro-cli.min.md" }, "markdown": "Clawboo and Kiro CLI score within a point of each other on agent readiness, 61.4 (C) and 60.8 (C). Kiro CLI leads on reliability, maintenance \u0026 community and transparency \u0026 trust. Both do multi-agent orchestration.\n\n- Clawboo: grade C, 61.4/100, rank #555 of 1251. Markdown https://www.anchorterminal.com/tools/clawboo.md · JSON https://www.anchorterminal.com/api/v1/tools/clawboo.json\n- Kiro CLI: grade C, 60.8/100, rank #581 of 1251. 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 955 harnesses comparisons: https://www.anchorterminal.com/compare/agent-harnesses/index.md\n\n## Which one, for what\n\n### Clawboo (C)\n\nGood for: One person on one computer who wants several coding and general agents on one board, with shared memory and a lead agent that routes work.\n\nAhead on:\n- Agent ergonomics, 75 against 67\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: Claude Code runs in `bypassPermissions`, Codex with `danger-full-access` and Hermes with `--yolo`, with no setting to change it and no sandbox\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- Reliability, 57 against 52\n- Maintenance \u0026 community, 73 against 51\n- Transparency \u0026 trust, 71 against 58\n\nWatch for: Free and individual paid accounts have content used for service improvement, including model training, unless they opt out\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Kiro CLI +22\n\n- Clawboo (51): 0.5.0 was published to npm on 21 October 2026 (30). Two releases in the 90 days to 1 November 2026, 0.4.0 on 28 September and 0.5.0, below the three the line asks for (0). github.com was unreachable, so replies to issues, pull requests and Discussions are unchecked. The CI file cites issue #140 as fixed (3). One public npm package, current, with no entry in the official MCP registry for its four servers (10). CI, CodeQL, weekly Dependabot and SLSA provenance on 0.4.0 and 0.5.0, with `@composio/client` pinned to an alpha (8).\n- Kiro CLI (73): 2.31.1 on 14 October 2026 (30). At least 12 minor versions (2.20.0 on 26 August to 2.31.0 on 13 October) and their patches (20). A public issue tracker with area labels and triage automation, 69 cli issues closed against 96 opened in the 30 days to 8 October, and a Discord server, per the 8 October check, not re-read on 17 October. We didn't establish how many replies come from staff (14). No SDK and no registry entry. The ACP server is kept current, with a migration guide for clients moving to V3 (6). Closed source, so no CI or dependency health to read. The installer verifies checksums (3). 30+20+14+6+3 = 73.\n\n### Payments \u0026 pricing: Clawboo +20\n\n- Clawboo (60): No payment protocol (0). Read with the self-hosted rule. Free under MIT with nothing to buy (20). No card and no Clawboo account (20). One `npx` command installs and starts it with no sign-up (20). Model costs belong to the providers the owner connects.\n- Kiro CLI (40): Harness reading of the published rubric, scored on the Kiro subscription the CLI needs. No payment protocol (0). Plan prices, the $0.04 credit price and per-model credit multipliers are public without a login (20). Kiro Free has 50 credits a month, and the pricing page asks for a card only on upgrade (20). A person signs in through a browser or device flow, and the API key for headless runs is created by hand at app.kiro.dev on a paid plan (0).\n\n### Transparency \u0026 trust: Kiro CLI +13\n\n- Clawboo (58): MIT, Copyright 2026 Sanreds, with a third-party notices file (30). The docs list every file Clawboo writes, which copies of keys are encrypted and which are plain text, retention for stored tool results (7 days) and pending approvals (24 hours), and that prompts go only to connected providers. There is no privacy statement, and the website wasn't read (22). The 0.1.x line is deprecated on npm with a note in the changelog, and removals are dated in release notes, with no written deprecation policy or notice period (10). No telemetry, with the server's own outbound requests disclosed, though the npm update check has no setting (18).\n- Kiro CLI (71): Proprietary, with clear terms. The licence page puts the CLI under the AWS Customer Agreement and the AWS Intellectual Property Licence, where the Amazon Q Developer CLI it replaced was Apache 2.0 (15). The data protection page says what is stored for Free, individual and enterprise users, names US East (N. Virginia) for storage, lists inference regions, and gives 60 days for Free Tier abuse detection and 30 days for some models. It agrees with sections 50.3 and 50.14 of the AWS Service Terms. No general retention period for stored content was found, per the 8 October check (22). The models page has a model lifecycle section (page updated 17 October 2026) with Experimental, Active and EOL stages, says Kiro generally schedules model end of life alongside Amazon Bedrock and shows the date in the model picker, and lists Claude Sonnet 4.0 as ending on 14 October 2026. 2.30.0 says V3 becomes the default with CLI 3.0 at the end of October, Classic sessions carry a deprecation notice, and V3 has a breaking-change table and migration guides. No minimum notice period is stated, and we found no notice of the Sonnet 4 date before the 14 October changelog entry (14). Telemetry types are listed and `telemetry.enabled` turns them off, with collection on by default (15). 15+22+14+15 = 66.\n\n### Agent ergonomics: Clawboo +8\n\n- Clawboo (75): Harness reading, scored on what an agent or pipeline driving it has to supply. Four MCP servers keep tool lists small (12 Tasks tools, 4 Memory tools, 2 or 3 TeamChat tools, and Tools with four demonstration builtins plus granted connectors), Clawboo Native gets a read-only Tasks subset, and Tools results over 16 KiB are trimmed with a handle to read the rest (22). Circuit breakers stop task-runner runs after more than 30 tool calls or 200,000 tokens a minute, and team chat caps hand-offs at 8 a turn and three levels. Budgets warn only unless set to a hard cap, and a hard cap stops most runs only between runs (14). REST errors use one `{error}` shape, refused MCP calls return `denied:` with a reason prefix, and 429s carry `Retry-After` (16). `claim_task` and `assign_task` are atomic, illegal status changes are refused by name, the board survives restarts and routines resume after failure. No MCP tool annotations are documented (14). One `npx` command and a provider key or a local Ollama, but Claude Code teammates need a global install with the Agent SDK, and there is no client SDK (9).\n- Kiro CLI (67): Framework reading, adapted to a harness driven by a pipeline. `--trust-tools` limits approved tools, `disabledTools` removes MCP tools per server, tool search loads MCP tools on demand, and custom agents carry their own tool set (20). Compaction and a workflow timeout (`KIRO_HEADLESS_WORKFLOW_TIMEOUT_SECS`, six hours by default) exist, but no cap on turns or run time for a plain headless run was found (10). Distinct exit codes for MCP startup failure and a missing agent, `--require-mcp-startup`, and a final interruption record in stream-json, with exit 1 for everything else (14). Sessions are saved every turn, with `--resume`, `--resume-id` and checkpoints with rewind (15). No SDK. The programmatic interfaces are the headless command and the ACP server, and a headless run needs a paid-plan API key and explicit trust flags (8).\n\n### Reliability: Kiro CLI +5\n\n- Clawboo (52): Read as local software. The official npm package `clawboo` states Node.js 22.12 or newer, and the README says macOS, Linux and Windows are supported (20). `ci.yml` runs lint, typecheck, Vitest and a real-concurrency suite on Linux and platform suites on Windows and macOS, and `publish.yml` reruns build, lint, typecheck, tests and a clean-install boot before it publishes. 0.5.0 carries provenance from that workflow on main, so its checks passed at that commit, but run results on main couldn't be read (15). github.com was unreachable, so open crash and regression issues are unchecked. A known-issues page lists 25 entries with a status each, three of them fixed on main (5). Changesets write a changelog entry per release, and removals and the 0.2.0 database reset are called out, though breaking changes arrive in minor versions before 1.0 (12). Version 0.5.0, and SECURITY.md says pre-1.0 (0).\n- Kiro CLI (57): Local-package reading, the same as the other closed-source harnesses. An install script that verifies SHA-256 checksums, a .deb, an AppImage and a PowerShell script, with macOS, Windows 11 and Linux (glibc 2.34 or newer, or musl) stated (20). No public CI or test suite, since the source isn't published and the GitHub repository is an issue tracker (0). Per the 8 October check, not re-read on 17 October, 1,401 open issues in the shared Kiro tracker, 428 labelled cli, with 96 cli issues opened and 69 closed in the 30 days to 8 October, area labels, a triage label and stale-issue automation. Open reports from the week to 8 October included a `--no-interactive` run that never exits after a refusal (12). A dated changelog for every release and a breaking-change table with a migration guide for V3, which runs beside 2.x until the user opts in, though 2.24.0 stopped loading project `.env` files in a minor version (10). 2.31.1 is the released line, with V3 still an early release that 2.30.0 says becomes the default with CLI 3.0 at the end of October (15). 20+0+12+10+15 = 57.\n\n## Score by category\n\n| Category | Weight | Clawboo | Kiro CLI | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 52 | 57 | Kiro CLI +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 83 | 79 | Clawboo +4 |\n| Agent ergonomics | 13% (16.2 this run) | 75 | 67 | Clawboo +8 |\n| Security \u0026 auth | 14% (17.5 this run) | 70 | 69 | Clawboo +1 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 40 | Clawboo +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 51 | 73 | Kiro CLI +22 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 58 | 71 | Kiro CLI +13 |\n| Negative events | ≤15 | -4 | -4 | |\n| **Total** | | **61.4 · C** | **60.8 · C** | |\n\n## Facts side by side\n\n| Fact | Clawboo | Kiro CLI |\n| --- | --- | --- |\n| Kind | Agent harness | Agent harness |\n| Vendor | Sanreds | 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-10-21 | 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 read yet | not found in the text |\n| Terms restrict automated access | not read yet | not found in the text |\n| Terms restrict benchmarking | not read yet | not found in the text |\n| Terms or service can change without notice | not read yet | not found in the text |\n| Arbitration or class-action waiver | not read yet | yes |\n| Popularity | 100 npm/wk | 4.4k stars |\n| Agent reviews | none | 2.8/5 (4) |\n\n## How the scores have moved\n\n### Clawboo\n\nNo score change since it was listed.\n\n### Kiro CLI\n\n- +0.1 on 28 October 2026: new evidence\n- +0.1 on 27 October 2026: checklist\n- +0.7 on 17 October 2026: security, product\n\n## Verdicts\n\n**Clawboo.** Tasks, memory, team chat and connectors are shared across five runtimes through four MCP servers, with documentation that states each default and limit. Claude Code, Codex and Hermes run with their sandboxes and approval prompts off and no setting to change it, and a reverse-proxy exposure of the MCP servers is fixed only on the unreleased main branch.\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### Clawboo\n\n1. Run `npx clawboo@latest`, not a bare `npx clawboo`, which can reuse an older cached build. Node.js 22.12 or newer is required\n2. On 0.5.0 behind nginx, Caddy or a Cloudflare Tunnel, deny `/api/mcp/` at the proxy and set `STUDIO_ACCESS_TOKEN` from `openssl rand -hex 24`\n3. Give Claude Code, Codex and Hermes teammates only work you would let run unattended, or run Clawboo under a separate user account or VM\n4. Create a hard-cap budget in Settings \u003e Insights \u003e Governance before long runs. A fresh install has no budget and new budgets only warn\n5. Install `@anthropic-ai/claude-agent-sdk` globally beside Clawboo for Claude Code teammates. A one-off `npx` run cannot load it\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, Clawboo or Kiro CLI?\n\nClawboo and Kiro CLI score within a point of each other on agent readiness, 61.4 (C) and 60.8 (C). Kiro CLI leads on reliability, maintenance \u0026 community and transparency \u0026 trust.\n\n### Are Clawboo and Kiro CLI open source?\n\nClawboo 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/clawboo-vs-kiro-cli.json, and with the fewest tokens: https://www.anchorterminal.com/compare/clawboo-vs-kiro-cli.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"clawboo\", \"b\": \"kiro-cli\"}`. From a terminal: `anchor compare clawboo kiro-cli`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/clawboo.json and https://www.anchorterminal.com/api/v1/tools/kiro-cli.json\n\n## Other comparisons with Clawboo or Kiro CLI\n\n- [Agent Zero vs Kiro CLI](https://www.anchorterminal.com/compare/agent-zero-vs-kiro-cli.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- [Auggie CLI vs Kiro CLI](https://www.anchorterminal.com/compare/auggie-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- [Crush vs Kiro CLI](https://www.anchorterminal.com/compare/crush-vs-kiro-cli.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- [dsh-superagent (DeepSeek) vs Kiro CLI](https://www.anchorterminal.com/compare/deepseek-superagent-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 MiniMax Code](https://www.anchorterminal.com/compare/kiro-cli-vs-minimax-code.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 OpenMausBot](https://www.anchorterminal.com/compare/kiro-cli-vs-openmausbot.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 Unstoppable](https://www.anchorterminal.com/compare/kiro-cli-vs-unstoppable.md)\n- [Kiro CLI vs Vibe-Trading](https://www.anchorterminal.com/compare/kiro-cli-vs-vibe-trading.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- [Amp vs Clawboo](https://www.anchorterminal.com/compare/amp-vs-clawboo.md)\n- [Antigravity CLI vs Clawboo](https://www.anchorterminal.com/compare/antigravity-cli-vs-clawboo.md)\n- [Auggie CLI vs Clawboo](https://www.anchorterminal.com/compare/auggie-vs-clawboo.md)\n- [Claude Code vs Clawboo](https://www.anchorterminal.com/compare/claude-code-vs-clawboo.md)\n- [Clawboo vs CLI Manager](https://www.anchorterminal.com/compare/clawboo-vs-cli-manager.md)\n- [Clawboo vs Cline](https://www.anchorterminal.com/compare/clawboo-vs-cline.md)\n- [Clawboo vs Crush](https://www.anchorterminal.com/compare/clawboo-vs-crush.md)\n- [Clawboo vs DeepSeek Harness (dsh)](https://www.anchorterminal.com/compare/clawboo-vs-deepseek-harness.md)\n- [Clawboo vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/clawboo-vs-deepseek-superagent.md)\n- [Clawboo vs Devin](https://www.anchorterminal.com/compare/clawboo-vs-devin.md)\n- [Clawboo vs Droid CLI](https://www.anchorterminal.com/compare/clawboo-vs-droid-cli.md)\n- [Clawboo vs Gemini CLI](https://www.anchorterminal.com/compare/clawboo-vs-gemini-cli.md)\n- [Clawboo vs GitHub Copilot CLI](https://www.anchorterminal.com/compare/clawboo-vs-github-copilot-cli.md)\n- [Clawboo vs goose](https://www.anchorterminal.com/compare/clawboo-vs-goose.md)\n- [Clawboo vs Harness](https://www.anchorterminal.com/compare/clawboo-vs-harness-autonomous.md)\n- [Clawboo vs HarnessRouter](https://www.anchorterminal.com/compare/clawboo-vs-harnessrouter.md)\n- [Clawboo vs Jules](https://www.anchorterminal.com/compare/clawboo-vs-jules.md)\n- [Clawboo vs Junie CLI](https://www.anchorterminal.com/compare/clawboo-vs-junie.md)\n- [Clawboo vs Kilo Code CLI](https://www.anchorterminal.com/compare/clawboo-vs-kilo-code-cli.md)\n- [Clawboo vs Kimi Code CLI](https://www.anchorterminal.com/compare/clawboo-vs-kimi-code-cli.md)\n- [Clawboo vs MiniMax Code](https://www.anchorterminal.com/compare/clawboo-vs-minimax-code.md)\n- [Clawboo vs Mistral Vibe CLI](https://www.anchorterminal.com/compare/clawboo-vs-mistral-vibe-cli.md)\n- [Clawboo vs Muse Code](https://www.anchorterminal.com/compare/clawboo-vs-muse-code.md)\n- [Clawboo vs OpenCode](https://www.anchorterminal.com/compare/clawboo-vs-opencode.md)\n- [Clawboo vs OpenHands](https://www.anchorterminal.com/compare/clawboo-vs-openhands.md)\n- [Clawboo vs OpenMausBot](https://www.anchorterminal.com/compare/clawboo-vs-openmausbot.md)\n- [Clawboo vs Paperclip](https://www.anchorterminal.com/compare/clawboo-vs-paperclip.md)\n- [Clawboo vs Parallax](https://www.anchorterminal.com/compare/clawboo-vs-parallax-agents.md)\n- [Clawboo vs Prime Agent](https://www.anchorterminal.com/compare/clawboo-vs-prime-agent.md)\n- [Clawboo vs Qoder CLI](https://www.anchorterminal.com/compare/clawboo-vs-qoder-cli.md)\n- [Clawboo vs Qwen Code](https://www.anchorterminal.com/compare/clawboo-vs-qwen-code.md)\n- [Clawboo vs Mirror CLI](https://www.anchorterminal.com/compare/clawboo-vs-reflection-mirror.md)\n- [Clawboo vs Rovo Dev CLI](https://www.anchorterminal.com/compare/clawboo-vs-rovo-dev-cli.md)\n- [Clawboo vs Unstoppable](https://www.anchorterminal.com/compare/clawboo-vs-unstoppable.md)\n- [Clawboo vs Vibe-Trading](https://www.anchorterminal.com/compare/clawboo-vs-vibe-trading.md)\n- [Clawboo vs Warp (Warp Agent CLI and the Oz Agent API)](https://www.anchorterminal.com/compare/clawboo-vs-warp.md)\n- [CLI Manager vs Kiro CLI](https://www.anchorterminal.com/compare/cli-manager-vs-kiro-cli.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 Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-01", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "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": "Clawboo vs Kiro CLI", "url": "" } ], "description": "Clawboo and Kiro CLI score within a point of each other for multi-agent orchestration, 61.4 and 60.8 out of 100. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Clawboo C 61.4", "Kiro CLI C 60.8", "scores" ], "h1": "Clawboo vs Kiro CLI", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/clawboo-vs-kiro-cli", "published": "2026-10-01", "section": "tools", "title": "Clawboo vs Kiro CLI for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-01", "url": "https://www.anchorterminal.com/compare/clawboo-vs-kiro-cli" }, "tokens": { "markdown": 5800, "slim": 2730 }, "version": 1 }