{ "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": "Kilo Code CLI scores 73 (BB) on agent readiness against Clawboo's 61.4 (C), and leads in 4 of 7 scored categories. Clawboo leads on security \u0026 auth and payments \u0026 pricing.", "b": { "slug": "kilo-code-cli", "name": "Kilo Code CLI", "vendor": "Kilo Code Inc.", "vendorUrl": "https://kilo.ai", "kind": "harness", "category": "agent-harnesses", "summary": "Open-source coding agent for the terminal, forked from opencode and built from the same repository as Kilo's VS Code and JetBrains extensions. It runs with your own provider key, a local model or the Kilo Gateway.", "url": "https://www.anchorterminal.com/tools/kilo-code-cli", "markdownUrl": "https://www.anchorterminal.com/tools/kilo-code-cli.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/kilo-code-cli.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/kilo-code-cli.json", "dns": "kilo-code-cli.grade.anchorterminal.com", "repo": "https://github.com/Kilo-Org/kilocode", "license": "MIT", "transports": [], "packages": [ { "registry": "npm", "name": "@kilocode/cli" }, { "registry": "npm", "name": "@kilocode/sdk" } ], "auth": "mixed", "authNotes": "Your own provider key in `~/.config/kilo/kilo.jsonc` or the environment, a local model, or a Kilo account through `kilo auth login` for the Kilo Gateway and its free models. `kilo serve` runs unauthenticated unless `KILO_SERVER_PASSWORD` is set.", "pricing": "freemium", "pricingNotes": "The CLI is free and MIT-licensed, and needs no Kilo account with your own key or a local model. Kilo Gateway credits are billed at provider rates with a 5 per cent fee on credit purchases. Kilo Pass starts at $19 a month, Teams is $15 a user a month and Enterprise is quoted. The pricing page says the free tier needs no card.", "priceSummary": "$19 / mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the pricing page or the README (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 27539, "npmWeekly": 32804, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://kilo.ai/docs/code-with-ai/platforms/cli", "llmsTxt": "https://kilo.ai/docs/llms.txt", "capabilities": [ "agent.harness", "agent.mcp-client", "agent.multi-agent" ], "tags": [ "harness", "coding-agent", "cli", "open-source", "typescript", "mcp", "llms-txt", "telemetry-default-on", "freemium", "no-card", "local" ], "lastRelease": "2026-10-15", "graded": true, "anchor": { "graded": true, "score": 73, "grade": "BB", "agentReady": true, "rank": 100, "ranked": true, "rankOf": 1251, "categoryRank": 3, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 72, "maintenance": 87, "payments": 50, "reliability": 85, "schema": 90, "security": 64, "transparency": 76 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-17" }, "negative": -2, "negativeNotes": [ "2026-10-14. 7.8.10 added the conda client ID to default-on telemetry. When `~/.conda/aau_token` exists the CLI runs `conda info --json --offline` and attaches the ID (`aauClientToken`) to every PostHog event, and a commit hashing it was reverted. Neither the changelog nor the docs mention it. It respects Kilo's opt-out and conda's `anaconda_anon_usage: false`. -2. https://github.com/Kilo-Org/kilocode/blob/main/packages/kilo-telemetry/src/conda.ts" ], "verdict": "Shell commands ask before running by default, and an optional operating-system sandbox blocks writes outside the workspace and outbound network. Telemetry to PostHog is on by default and the sandbox is off, so an unattended `kilo run --auto` approves everything not denied unless both are configured first.", "bestFor": "Developers who want an open-source terminal agent with per-tool permission rules, an optional sandbox and a choice of provider, and the same engine in VS Code and JetBrains.", "strengths": [ "Permission rules of `allow`, `ask` or `deny` per tool with glob patterns, and shell commands asking by default outside a built-in allow list", "A sandbox on macOS and Linux that limits writes, blocks network by default and refuses to run when it can't be enforced", "Project config can't weaken the sandbox or read environment variables through `{env:VAR}`", "Your own provider key or a local model works with no Kilo account", "Releases most weeks, with 7.8.9, 7.8.10 and 7.8.12 between 13 and 15 October 2026" ], "weaknesses": [ "Telemetry to PostHog is on by default, attaches the conda client ID since 7.8.10, and the privacy policy doesn't mention it", "The sandbox is off by default and unavailable on Windows", "`kilo run` lists no flag for a turn, time or cost limit", "The terms grant a perpetual licence to use uploaded Customer Data to improve Kilo's services", "SECURITY.md still says the CLI has no sandbox, and NVD records an unanswered low-severity CVE from May 2026" ], "agentNotes": [ "Set `sandbox.enabled` to true in the global `kilo.jsonc` before `kilo run --auto`. `--auto` approves every permission request not explicitly denied", "Set `experimental.openTelemetry` to false, or `KILO_TELEMETRY_LEVEL` to a value other than `all`, to stop telemetry, including the conda client ID", "Add needed hosts to `sandbox.allowed_hosts` in global config. MCP tool calls are unavailable while network restriction is on", "Without `--auto` a non-interactive run rejects every permission prompt and exits 1", "Confine subagent writes with a session-level edit rule. From 7.8.13 a custom agent's own `edit` denies no longer bind the subagents it starts" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 4, "avgRating": 2.3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 73 } ], "editorialScores": { "ergonomics": 72, "maintenance": 87, "payments": 50, "reliability": 85, "schema": 90, "security": 64, "transparency": 61 }, "provenanceScore": 90, "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-17", "oldest": "2026-10-17", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install -g @kilocode/cli # or: brew install Kilo-Org/tap/kilo", "headless": { "command": "kilo run --auto --format json \"$TASK\"" } }, "letme": { "capability": "https://letme.dev/agent.harness", "tool": "https://letme.dev/kilo-code-cli" }, "area": "frameworks", "unitPrices": [ { "item": "Kilo Pass, entry tier", "unit": "month", "usd": 19, "note": "monthly model credits with bonus credits, optional" }, { "item": "Teams plan", "unit": "seat-month", "usd": 15, "note": "model use billed separately at provider rates" } ], "provenance": { "legalEntity": "Kilo Code Inc. (the terms are a contract with Anaconda, Inc. on behalf of itself and its affiliates, including Kilo Code Inc.)", "domain": "kilo.ai", "domainRegistered": "2017-12-16", "endpointOnVendorDomain": null, "terms": "https://kilo.ai/terms", "privacy": "https://kilo.ai/privacy", "statusPage": "https://status.kilo.ai", "changelog": "https://github.com/Kilo-Org/kilocode/blob/main/packages/opencode/CHANGELOG.md", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The terms (last updated 30 September 2026) name the CLI among the services they cover and are made with Anaconda, Inc. The privacy policy (29 May 2026) names Kilo Code Inc. as data controller.", "kilo.ai/.well-known/security.txt lists security@kilo.ai and the policy at kilo.ai/security, names the CLI in scope and expires on 2026-12-31.", "trust.kilo.ai redirects to trust.anaconda.com, which has a Kilo Code section.", "status.kilo.ai is a Statuspage site for the website, gateway and cloud platform. The CLI runs on the owner's machine.", "PRIVACY.md in the repository is a separate short policy for the CLI dated March 2025." ], "score": 90 }, "requirements": { "card": "no", "freeTier": true, "minutes": 3, "credential": "mixed", "hosting": [ "self-hosted" ], "euResidency": "unknown", "trainsOnData": "unknown", "zeroRetention": "unknown", "selfHost": "yes" }, "pageJsonUrl": "https://www.anchorterminal.com/tools/kilo-code-cli.json", "live": { "slug": "kilo-code-cli", "vendorStatus": { "page": "https://status.kilo.ai", "indicator": "maintenance", "summary": "Service Under Maintenance", "checkedAt": "2026-11-01T05:14:53.830311882Z" }, "versions": [ { "registry": "github", "name": "Kilo-Org/kilocode", "version": "v7.8.18", "released": "2026-10-26", "seenAt": "2026-10-31T16:02:09.785975732Z" }, { "registry": "npm", "name": "@kilocode/cli", "version": "7.8.18", "seenAt": "2026-10-31T16:02:07.583270475Z" }, { "registry": "npm", "name": "@kilocode/sdk", "version": "7.8.18", "seenAt": "2026-10-31T16:02:08.431225527Z" } ], "githubStars": 27818, "npmWeekly": 57470, "securityTxt": { "url": "https://kilo.ai/.well-known/security.txt", "state": "valid", "expires": "2026-12-31T23:59:59.000Z", "checkedAt": "2026-10-31T15:40:23.001073315Z" }, "llmsTxt": { "url": "https://kilo.ai/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-31T15:11:04.13228791Z" }, "domain": { "domain": "kilo.ai", "registered": "2017-12-16", "source": "https://rdap.identitydigital.services/rdap/domain/kilo.ai", "checkedAt": "2026-10-25T13:54:23.157740908Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/Kilo-Org/kilocode/main/packages/opencode/CHANGELOG.md", "kind": "changelog", "status": 304, "checkedAt": "2026-10-31T06:19:41.237809173Z", "changedAt": "2026-10-29T05:14:29.778937453Z", "fingerprint": "e62a422384a5" }, { "url": "https://kilo.ai/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-31T06:14:24.971168357Z", "changedAt": "2026-10-21T00:28:45.897088737Z", "fingerprint": "438622fad605" }, { "url": "https://kilo.ai/terms", "kind": "terms", "status": 200, "checkedAt": "2026-10-31T06:14:27.216411661Z", "changedAt": "2026-10-21T00:28:48.139673985Z", "fingerprint": "ab8895c68f21" } ], "github": { "repo": "kilo-org/kilocode", "checkedAt": "2026-10-26T07:37:46.421102244Z", "stars": 27753, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-25T18:19:48Z", "openIssues": 577, "openPRs": 197, "issuesOpened90d": 922, "issuesClosed90d": 934, "prsMerged90d": 1426, "ci": { "branch": "main", "runs": 50, "success": 50, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-10-23T17:23:45Z" }, "replies": { "sampled": 5, "unanswered": 4, "medianDays": 1.7 } }, "updatedAt": "2026-11-01T05:14:53.830311882Z" } }, "edges": [ { "by": 36, "category": "maintenance", "leads": "kilo-code-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": "7.8.12 on the npm `latest` tag on 15 October 2026, with 7.8.13 and 7.8.14 on the `rc` tag on 16 October (30). 7.8.9, 7.8.10 and 7.8.12 since the 8 October check, and 46 versions published to npm since 17 July 2026, two of them on the `rc` tag (20). The newest issues carry area and triage labels from automation, but the 15 newest open issues had no or one comment each on 8 October, against 448 open issues and 147 open pull requests, per the 8 October check, not re-read on 17 October (15). `@kilocode/sdk` is at 7.8.12 with the CLI, and the VS Code extension ships from the same release workflow (13). CI, CodeQL and Dependabot security updates run, with version updates switched off because most dependencies arrive through merges from opencode (9)." }, "scores": { "a": 51, "b": 87 } }, { "by": 33, "category": "reliability", "leads": "kilo-code-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. `@kilocode/cli` on npm, a Homebrew tap, an AUR package, an install script and release binaries for Linux, macOS and Windows on x64 and arm64, with baseline and musl builds named (20). Public CI, and the 40 most recent completed workflow runs on main on 8 October 2026 all succeeded, the test, typecheck and VS Code test workflows among them, per the 8 October check, not re-read on 17 October (25). 448 open issues and 147 open pull requests, a workflow that closes issues after 60 quiet days and pull requests after 30, and open reports from 7 October of a turn that hangs after the loop exits (#14876) and of exhausted 503 retries ending a run with no visible error (#14877), per the 8 October check, not re-read on 17 October (15). The CLI changelog is generated by Changesets with Minor and Patch headings and no dates or breaking-change headings. 7.8.13 (rc on 16 October) changes how a custom agent's edit denies apply to its subagents under a Patch heading (10). 7.8.12 on the npm `latest` tag, past 1.0 (15)." }, "scores": { "a": 52, "b": 85 } }, { "by": 18, "category": "transparency", "leads": "kilo-code-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": "MIT, with opencode's copyright kept in the licence file (30). The privacy policy (29 May 2026) names Kilo Code Inc. as controller, says data is stored in the United States and lists Stripe, OpenRouter, model providers, AppsFlyer and Sentry, but it doesn't mention the CLI's PostHog telemetry. PRIVACY.md in the repository is dated March 2025 and is silent on telemetry too. The terms (30 September 2026) are a contract with Anaconda, Inc. and grant a perpetual licence to use uploaded Customer Data to improve the services (13). `kilo console` is marked deprecated with no removal date, and updated terms apply after 30 days. No written deprecation policy found (8). The docs say telemetry is on by default and name the opt-out key in two places, without listing what is collected or where it goes (10)." }, "scores": { "a": 58, "b": 76 } }, { "by": 10, "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": "No payment protocol (0). Scored on Kilo's paid options, as with Cline. Plan prices are public (Kilo Pass from $19 a month, Teams $15 a user a month, Enterprise by quote) and the gateway bills provider rates plus a 5 per cent fee on credit purchases, but the pricing page carries no per-token list (10). The CLI is MIT-licensed and free. The no-card statement seen on 8 October wasn't in the pricing page text on 17 October, but nothing has to be bought to use the CLI with your own key (20). Your own provider key or a local model works with no Kilo account, so an agent can install and run it without a sign-up (20)." }, "scores": { "a": 60, "b": 50 } }, { "by": 7, "category": "schema", "leads": "kilo-code-cli", "name": "Schema \u0026 documentation", "reasons": { "a": "Harness reading of the framework line, as for Paperclip. The REST API's 199 routes are documented per resource with parameters, bodies and responses, and the MCP tools reference gives typed arguments for every tool on the four servers, but no OpenAPI file was found (17). llms.txt, llms-full.txt and a Markdown copy of every page at `.md` on docs.claw.boo (10). The docs say what each part does and does not cover, with known issues, production defaults and a limits page that names the code line behind each number (17). Tool arguments are typed with required and optional fields and documented caps, such as 24 live subtasks per parent and limits lowered to 1,000, with free-text task bodies (12). curl examples on each API page, an events and errors reference, and the exact error strings each MCP tool returns (14). A dated changelog for every release with an Unreleased section, though API paths carry no version and every MCP server reports 0.1.0 (13).", "b": "Framework reading. A JSON Schema for `kilo.jsonc` at `https://app.kilo.ai/config.json`, an OpenAPI file for the `kilo serve` API at `packages/sdk/openapi.json` and a CLI reference generated from the command definitions (25). `llms.txt` on kilo.ai and on the docs, the second listing a raw Markdown address for every page (10). The sandboxing page says when to use the sandbox, what it does not protect and how it differs from permissions (16). Permissions are `allow`, `ask` or `deny` with glob rules, `sandbox.network` and `--format` are enums, though the schema served on 8 October had no `sandbox` key (13). Config and CI samples and exit codes 0, 1 and 124, but we found no reference for the records `--format json` writes (11). A versioned changelog and dated GitHub releases (15)." }, "scores": { "a": 83, "b": 90 } }, { "by": 6, "category": "security", "leads": "clawboo", "name": "Security \u0026 auth", "reasons": { "a": "Harness reading of the framework checklist, as for the other harnesses. 30 for what leaves the machine by default, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. The docs say Clawboo sends no telemetry and list the GitHub catalogue fetch, the npm version check, OpenRouter's public model list, Google Fonts and the GitHub star count, of which only the catalogue address can be changed (27). Clawboo Native shell commands are off by default and asked one at a time, and connector grants are per agent with approval on writes. Claude Code, Codex and Hermes run with their prompts and sandboxes off and no setting to change it, they can read Clawboo's database and key vault, and with no access token by default any local program can answer approval cards (8). Images in agent text don't load on their own, peer posts are marked as evidence, and a run that has read private data and untrusted content asks before any outbound connector call (11). An audit log of budget, breaker, approval, verification, tool-call and install events, with secrets masked (13). SECURITY.md with private reporting, CodeQL, Dependabot and npm provenance. No security.txt or bug bounty, OSV lists no advisory for `clawboo`, and the proxy advisory is on the docs with a workaround while its fix is unreleased (11).", "b": "Harness reading of the framework checklist. 30 for what leaves the machine by default, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. Telemetry is on by default and goes to PostHog in the United States, the source links the machine identifier to the account email after a Kilo sign-in, and since 7.8.10 (14 October) it also attaches the conda client ID when `~/.conda/aau_token` exists (see negative). It is turned off with `experimental.openTelemetry` or `KILO_TELEMETRY_LEVEL`. Provider keys stay on the machine (14). Shell commands ask by default outside a built-in allow list, reads of `.env` files and paths outside the project ask, and edits inside the project run without asking. An operating-system sandbox (Seatbelt on macOS, Bubblewrap on Linux, none on Windows) limits writes and blocks the network, refuses to run when it can't be enforced, and is off by default. `--auto` approves everything not explicitly denied (15). The sandboxing page covers prompt injection and its limits, project config can't weaken the sandbox, and `{env:VAR}` is resolved only in trusted config (11). Session export, `kilo stats` and OTLP export of traces and logs, with audit logs on the Enterprise plan (12). A valid security.txt (expires 2026-12-31), a disclosure policy that cites HackerOne's standards and safe harbour, CodeQL in CI and no published repository advisories. NVD lists CVE-2026-8766 (low, through 7.0.47, May 2026) and says the vendor didn't respond, and SECURITY.md still says the CLI has no sandbox (12)." }, "scores": { "a": 70, "b": 64 } } ], "facts": [ { "a": "Agent harness", "b": "Agent harness", "name": "Kind" }, { "a": "Sanreds", "b": "Kilo Code Inc.", "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": "MIT", "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-15", "name": "Last release" }, { "a": "no document linked", "b": "2026-09-30", "name": "Terms last updated" }, { "a": "no document linked", "b": "2026-05-29", "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": "yes", "name": "Terms restrict automated access" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not read yet", "b": "yes", "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": "28k stars, 33k npm/wk", "name": "Popularity" }, { "a": "none", "b": "2.3/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "Kilo Code CLI scores 73 (BB) on agent readiness against Clawboo's 61.4 (C), and leads in 4 of 7 scored categories. Clawboo leads on security \u0026 auth and payments \u0026 pricing.", "question": "Which is better for AI agents, Clawboo or Kilo Code CLI?" }, { "answer": "Yes. Clawboo is open source (MIT). Kilo Code CLI is open source (MIT).", "question": "Are Clawboo and Kilo Code CLI open source?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 70 against 64", "Payments \u0026 pricing, 60 against 50" ], "also": [ "No key needed to call it" ], "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, 85 against 52", "Schema \u0026 documentation, 90 against 83", "Maintenance \u0026 community, 87 against 51", "Transparency \u0026 trust, 76 against 58" ], "also": [ "Agent-ready, a grade of BB or better" ], "goodFor": "Developers who want an open-source terminal agent with per-tool permission rules, an optional sandbox and a choice of provider, and the same engine in VS Code and JetBrains.", "slug": "kilo-code-cli", "watchFor": "Telemetry to PostHog is on by default, attaches the conda client ID since 7.8.10, and the privacy policy doesn't mention it" } ], "history": { "clawboo": null, "kilo-code-cli": [ { "causes": [ "evidence", "event" ], "date": "2026-10-17", "delta": -2.4, "from": 75.4, "fromGrade": "BB", "to": 73, "toGrade": "BB" } ] }, "job": { "capability": "agent.multi-agent", "name": "Multi-agent orchestration" }, "others": [ { "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/aider-vs-kilo-code-cli.json", "title": "Aider vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/aider-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/amp-vs-kilo-code-cli.json", "title": "Amp vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/amp-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/antigravity-cli-vs-kilo-code-cli.json", "title": "Antigravity CLI vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/antigravity-cli-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/auggie-vs-kilo-code-cli.json", "title": "Auggie CLI vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/auggie-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/claude-code-vs-kilo-code-cli.json", "title": "Claude Code vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/claude-code-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/cline-vs-kilo-code-cli.json", "title": "Cline vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/cline-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-kilo-code-cli.json", "title": "Crush vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/crush-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/cursor-cli-vs-kilo-code-cli.json", "title": "Cursor CLI vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/cursor-cli-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/deepseek-harness-vs-kilo-code-cli.json", "title": "DeepSeek Harness (dsh) vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/deepseek-harness-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-kilo-code-cli.json", "title": "dsh-superagent (DeepSeek) vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/devin-vs-kilo-code-cli.json", "title": "Devin vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/devin-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/droid-cli-vs-kilo-code-cli.json", "title": "Droid CLI vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/droid-cli-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/earendil-pi-vs-kilo-code-cli.json", "title": "Pi vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/earendil-pi-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/gemini-cli-vs-kilo-code-cli.json", "title": "Gemini CLI vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/gemini-cli-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/github-copilot-cli-vs-kilo-code-cli.json", "title": "GitHub Copilot CLI vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/github-copilot-cli-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/goose-vs-kilo-code-cli.json", "title": "goose vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/goose-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/harness2-vs-kilo-code-cli.json", "title": "Harness² vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/harness2-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-kilo-code-cli.json", "title": "HarnessRouter vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/jules-vs-kilo-code-cli.json", "title": "Jules vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/jules-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/junie-vs-kilo-code-cli.json", "title": "Junie CLI vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/junie-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-kimi-code-cli.json", "title": "Kilo Code CLI vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-kimi-code-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/kilo-code-cli-vs-mini-swe-agent.json", "title": "Kilo Code CLI vs mini-swe-agent", "url": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-mini-swe-agent" }, { "json": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-minimax-code.json", "title": "Kilo Code CLI vs MiniMax Code", "url": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-minimax-code" }, { "json": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-mistral-vibe-cli.json", "title": "Kilo Code CLI vs Mistral Vibe CLI", "url": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-mistral-vibe-cli" }, { "json": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-muse-code.json", "title": "Kilo Code CLI vs Muse Code", "url": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-muse-code" }, { "json": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-openai-codex.json", "title": "Kilo Code CLI vs OpenAI Codex", "url": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-openai-codex" }, { "json": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-opencode.json", "title": "Kilo Code CLI vs OpenCode", "url": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-opencode" }, { "json": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-openhands.json", "title": "Kilo Code CLI vs OpenHands", "url": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-openhands" }, { "json": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-openmausbot.json", "title": "Kilo Code CLI vs OpenMausBot", "url": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-openmausbot" }, { "json": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-prime-agent.json", "title": "Kilo Code CLI vs Prime Agent", "url": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-prime-agent" }, { "json": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-qoder-cli.json", "title": "Kilo Code CLI vs Qoder CLI", "url": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-qoder-cli" }, { "json": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-qwen-code.json", "title": "Kilo Code CLI vs Qwen Code", "url": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-qwen-code" }, { "json": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-reflection-mirror.json", "title": "Kilo Code CLI vs Mirror CLI", "url": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-reflection-mirror" }, { "json": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-rovo-dev-cli.json", "title": "Kilo Code CLI vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-unstoppable.json", "title": "Kilo Code CLI vs Unstoppable", "url": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-unstoppable" }, { "json": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-vibe-trading.json", "title": "Kilo Code CLI vs Vibe-Trading", "url": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-vibe-trading" }, { "json": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-warp.json", "title": "Kilo Code CLI vs Warp (Warp Agent CLI and the Oz Agent API)", "url": "https://www.anchorterminal.com/compare/kilo-code-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-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-kiro-cli.json", "title": "Clawboo vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/clawboo-vs-kiro-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-kilo-code-cli.json", "title": "CLI Manager vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/cli-manager-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/harness-autonomous-vs-kilo-code-cli.json", "title": "Harness vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/harness-autonomous-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-paperclip.json", "title": "Kilo Code CLI vs Paperclip", "url": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-paperclip" }, { "json": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-parallax-agents.json", "title": "Kilo Code CLI vs Parallax", "url": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-parallax-agents" } ], "panel": null, "scores": [ { "by": 33, "clawboo": 52, "edge": "kilo-code-cli", "key": "reliability", "kilo-code-cli": 85, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 7, "clawboo": 83, "edge": "kilo-code-cli", "key": "schema", "kilo-code-cli": 90, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 3, "clawboo": 75, "edge": "clawboo", "key": "ergonomics", "kilo-code-cli": 72, "name": "Agent ergonomics", "weight": 13 }, { "by": 6, "clawboo": 70, "edge": "clawboo", "key": "security", "kilo-code-cli": 64, "name": "Security \u0026 auth", "weight": 14 }, { "by": 10, "clawboo": 60, "edge": "clawboo", "key": "payments", "kilo-code-cli": 50, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 36, "clawboo": 51, "edge": "kilo-code-cli", "key": "maintenance", "kilo-code-cli": 87, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 18, "clawboo": 58, "edge": "kilo-code-cli", "key": "transparency", "kilo-code-cli": 76, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Kilo Code CLI scores 73 (BB) on agent readiness against Clawboo's 61.4 (C), and leads in 4 of 7 scored categories. Clawboo leads on security \u0026 auth and payments \u0026 pricing. 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.", "kilo-code-cli": "Shell commands ask before running by default, and an optional operating-system sandbox blocks writes outside the workspace and outbound network. Telemetry to PostHog is on by default and the sandbox is off, so an unattended `kilo run --auto` approves everything not denied unless both are configured first." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/clawboo-vs-kilo-code-cli", "json": "https://www.anchorterminal.com/compare/clawboo-vs-kilo-code-cli.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/clawboo-vs-kilo-code-cli.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/clawboo-vs-kilo-code-cli.min.md" }, "markdown": "Kilo Code CLI scores 73 (BB) on agent readiness against Clawboo's 61.4 (C), and leads in 4 of 7 scored categories. Clawboo leads on security \u0026 auth and payments \u0026 pricing. 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- Kilo Code CLI: grade BB, 73/100, rank #100 of 1251. Markdown https://www.anchorterminal.com/tools/kilo-code-cli.md · JSON https://www.anchorterminal.com/api/v1/tools/kilo-code-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- Security \u0026 auth, 70 against 64\n- Payments \u0026 pricing, 60 against 50\n\nAlso in its favour:\n- No key needed to call it\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### Kilo Code CLI (BB)\n\nGood for: Developers who want an open-source terminal agent with per-tool permission rules, an optional sandbox and a choice of provider, and the same engine in VS Code and JetBrains.\n\nAhead on:\n- Reliability, 85 against 52\n- Schema \u0026 documentation, 90 against 83\n- Maintenance \u0026 community, 87 against 51\n- Transparency \u0026 trust, 76 against 58\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n\nWatch for: Telemetry to PostHog is on by default, attaches the conda client ID since 7.8.10, and the privacy policy doesn't mention it\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Kilo Code CLI +36\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- Kilo Code CLI (87): 7.8.12 on the npm `latest` tag on 15 October 2026, with 7.8.13 and 7.8.14 on the `rc` tag on 16 October (30). 7.8.9, 7.8.10 and 7.8.12 since the 8 October check, and 46 versions published to npm since 17 July 2026, two of them on the `rc` tag (20). The newest issues carry area and triage labels from automation, but the 15 newest open issues had no or one comment each on 8 October, against 448 open issues and 147 open pull requests, per the 8 October check, not re-read on 17 October (15). `@kilocode/sdk` is at 7.8.12 with the CLI, and the VS Code extension ships from the same release workflow (13). CI, CodeQL and Dependabot security updates run, with version updates switched off because most dependencies arrive through merges from opencode (9).\n\n### Reliability: Kilo Code CLI +33\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- Kilo Code CLI (85): Local-package reading. `@kilocode/cli` on npm, a Homebrew tap, an AUR package, an install script and release binaries for Linux, macOS and Windows on x64 and arm64, with baseline and musl builds named (20). Public CI, and the 40 most recent completed workflow runs on main on 8 October 2026 all succeeded, the test, typecheck and VS Code test workflows among them, per the 8 October check, not re-read on 17 October (25). 448 open issues and 147 open pull requests, a workflow that closes issues after 60 quiet days and pull requests after 30, and open reports from 7 October of a turn that hangs after the loop exits (#14876) and of exhausted 503 retries ending a run with no visible error (#14877), per the 8 October check, not re-read on 17 October (15). The CLI changelog is generated by Changesets with Minor and Patch headings and no dates or breaking-change headings. 7.8.13 (rc on 16 October) changes how a custom agent's edit denies apply to its subagents under a Patch heading (10). 7.8.12 on the npm `latest` tag, past 1.0 (15).\n\n### Transparency \u0026 trust: Kilo Code CLI +18\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- Kilo Code CLI (76): MIT, with opencode's copyright kept in the licence file (30). The privacy policy (29 May 2026) names Kilo Code Inc. as controller, says data is stored in the United States and lists Stripe, OpenRouter, model providers, AppsFlyer and Sentry, but it doesn't mention the CLI's PostHog telemetry. PRIVACY.md in the repository is dated March 2025 and is silent on telemetry too. The terms (30 September 2026) are a contract with Anaconda, Inc. and grant a perpetual licence to use uploaded Customer Data to improve the services (13). `kilo console` is marked deprecated with no removal date, and updated terms apply after 30 days. No written deprecation policy found (8). The docs say telemetry is on by default and name the opt-out key in two places, without listing what is collected or where it goes (10).\n\n### Payments \u0026 pricing: Clawboo +10\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- Kilo Code CLI (50): No payment protocol (0). Scored on Kilo's paid options, as with Cline. Plan prices are public (Kilo Pass from $19 a month, Teams $15 a user a month, Enterprise by quote) and the gateway bills provider rates plus a 5 per cent fee on credit purchases, but the pricing page carries no per-token list (10). The CLI is MIT-licensed and free. The no-card statement seen on 8 October wasn't in the pricing page text on 17 October, but nothing has to be bought to use the CLI with your own key (20). Your own provider key or a local model works with no Kilo account, so an agent can install and run it without a sign-up (20).\n\n### Schema \u0026 documentation: Kilo Code CLI +7\n\n- Clawboo (83): Harness reading of the framework line, as for Paperclip. The REST API's 199 routes are documented per resource with parameters, bodies and responses, and the MCP tools reference gives typed arguments for every tool on the four servers, but no OpenAPI file was found (17). llms.txt, llms-full.txt and a Markdown copy of every page at `.md` on docs.claw.boo (10). The docs say what each part does and does not cover, with known issues, production defaults and a limits page that names the code line behind each number (17). Tool arguments are typed with required and optional fields and documented caps, such as 24 live subtasks per parent and limits lowered to 1,000, with free-text task bodies (12). curl examples on each API page, an events and errors reference, and the exact error strings each MCP tool returns (14). A dated changelog for every release with an Unreleased section, though API paths carry no version and every MCP server reports 0.1.0 (13).\n- Kilo Code CLI (90): Framework reading. A JSON Schema for `kilo.jsonc` at `https://app.kilo.ai/config.json`, an OpenAPI file for the `kilo serve` API at `packages/sdk/openapi.json` and a CLI reference generated from the command definitions (25). `llms.txt` on kilo.ai and on the docs, the second listing a raw Markdown address for every page (10). The sandboxing page says when to use the sandbox, what it does not protect and how it differs from permissions (16). Permissions are `allow`, `ask` or `deny` with glob rules, `sandbox.network` and `--format` are enums, though the schema served on 8 October had no `sandbox` key (13). Config and CI samples and exit codes 0, 1 and 124, but we found no reference for the records `--format json` writes (11). A versioned changelog and dated GitHub releases (15).\n\n### Security \u0026 auth: Clawboo +6\n\n- Clawboo (70): Harness reading of the framework checklist, as for the other harnesses. 30 for what leaves the machine by default, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. The docs say Clawboo sends no telemetry and list the GitHub catalogue fetch, the npm version check, OpenRouter's public model list, Google Fonts and the GitHub star count, of which only the catalogue address can be changed (27). Clawboo Native shell commands are off by default and asked one at a time, and connector grants are per agent with approval on writes. Claude Code, Codex and Hermes run with their prompts and sandboxes off and no setting to change it, they can read Clawboo's database and key vault, and with no access token by default any local program can answer approval cards (8). Images in agent text don't load on their own, peer posts are marked as evidence, and a run that has read private data and untrusted content asks before any outbound connector call (11). An audit log of budget, breaker, approval, verification, tool-call and install events, with secrets masked (13). SECURITY.md with private reporting, CodeQL, Dependabot and npm provenance. No security.txt or bug bounty, OSV lists no advisory for `clawboo`, and the proxy advisory is on the docs with a workaround while its fix is unreleased (11).\n- Kilo Code CLI (64): Harness reading of the framework checklist. 30 for what leaves the machine by default, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. Telemetry is on by default and goes to PostHog in the United States, the source links the machine identifier to the account email after a Kilo sign-in, and since 7.8.10 (14 October) it also attaches the conda client ID when `~/.conda/aau_token` exists (see negative). It is turned off with `experimental.openTelemetry` or `KILO_TELEMETRY_LEVEL`. Provider keys stay on the machine (14). Shell commands ask by default outside a built-in allow list, reads of `.env` files and paths outside the project ask, and edits inside the project run without asking. An operating-system sandbox (Seatbelt on macOS, Bubblewrap on Linux, none on Windows) limits writes and blocks the network, refuses to run when it can't be enforced, and is off by default. `--auto` approves everything not explicitly denied (15). The sandboxing page covers prompt injection and its limits, project config can't weaken the sandbox, and `{env:VAR}` is resolved only in trusted config (11). Session export, `kilo stats` and OTLP export of traces and logs, with audit logs on the Enterprise plan (12). A valid security.txt (expires 2026-12-31), a disclosure policy that cites HackerOne's standards and safe harbour, CodeQL in CI and no published repository advisories. NVD lists CVE-2026-8766 (low, through 7.0.47, May 2026) and says the vendor didn't respond, and SECURITY.md still says the CLI has no sandbox (12).\n\n## Score by category\n\n| Category | Weight | Clawboo | Kilo Code CLI | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 52 | 85 | Kilo Code CLI +33 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 83 | 90 | Kilo Code CLI +7 |\n| Agent ergonomics | 13% (16.2 this run) | 75 | 72 | Clawboo +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 70 | 64 | Clawboo +6 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 50 | Clawboo +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 51 | 87 | Kilo Code CLI +36 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 58 | 76 | Kilo Code CLI +18 |\n| Negative events | ≤15 | -4 | -2 | |\n| **Total** | | **61.4 · C** | **73 · BB** | |\n\n## Facts side by side\n\n| Fact | Clawboo | Kilo Code CLI |\n| --- | --- | --- |\n| Kind | Agent harness | Agent harness |\n| Vendor | Sanreds | Kilo Code Inc. |\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 | MIT |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-21 | 2026-10-15 |\n| Terms last updated | no document linked | 2026-09-30 |\n| Privacy policy last updated | no document linked | 2026-05-29 |\n| Customer content may train models | not read yet | not found in the text |\n| Terms restrict automated access | not read yet | yes |\n| Terms restrict benchmarking | not read yet | not found in the text |\n| Terms or service can change without notice | not read yet | yes |\n| Arbitration or class-action waiver | not read yet | yes |\n| Popularity | 100 npm/wk | 28k stars, 33k npm/wk |\n| Agent reviews | none | 2.3/5 (4) |\n\n## How the scores have moved\n\n### Clawboo\n\nNo score change since it was listed.\n\n### Kilo Code CLI\n\n- -2.4 on 17 October 2026: new evidence, negative event\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**Kilo Code CLI.** Shell commands ask before running by default, and an optional operating-system sandbox blocks writes outside the workspace and outbound network. Telemetry to PostHog is on by default and the sandbox is off, so an unattended `kilo run --auto` approves everything not denied unless both are configured first.\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### Kilo Code CLI\n\n1. Set `sandbox.enabled` to true in the global `kilo.jsonc` before `kilo run --auto`. `--auto` approves every permission request not explicitly denied\n2. Set `experimental.openTelemetry` to false, or `KILO_TELEMETRY_LEVEL` to a value other than `all`, to stop telemetry, including the conda client ID\n3. Add needed hosts to `sandbox.allowed_hosts` in global config. MCP tool calls are unavailable while network restriction is on\n4. Without `--auto` a non-interactive run rejects every permission prompt and exits 1\n5. Confine subagent writes with a session-level edit rule. From 7.8.13 a custom agent's own `edit` denies no longer bind the subagents it starts\n\n## Questions\n\n### Which is better for AI agents, Clawboo or Kilo Code CLI?\n\nKilo Code CLI scores 73 (BB) on agent readiness against Clawboo's 61.4 (C), and leads in 4 of 7 scored categories. Clawboo leads on security \u0026 auth and payments \u0026 pricing.\n\n### Are Clawboo and Kilo Code CLI open source?\n\nYes. Clawboo is open source (MIT). Kilo Code CLI is open source (MIT).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/clawboo-vs-kilo-code-cli.json, and with the fewest tokens: https://www.anchorterminal.com/compare/clawboo-vs-kilo-code-cli.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"clawboo\", \"b\": \"kilo-code-cli\"}`. From a terminal: `anchor compare clawboo kilo-code-cli`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/clawboo.json and https://www.anchorterminal.com/api/v1/tools/kilo-code-cli.json\n\n## Other comparisons with Clawboo or Kilo Code CLI\n\n- [Agent Zero vs Kilo Code CLI](https://www.anchorterminal.com/compare/agent-zero-vs-kilo-code-cli.md)\n- [Aider vs Kilo Code CLI](https://www.anchorterminal.com/compare/aider-vs-kilo-code-cli.md)\n- [Amp vs Kilo Code CLI](https://www.anchorterminal.com/compare/amp-vs-kilo-code-cli.md)\n- [Antigravity CLI vs Kilo Code CLI](https://www.anchorterminal.com/compare/antigravity-cli-vs-kilo-code-cli.md)\n- [Auggie CLI vs Kilo Code CLI](https://www.anchorterminal.com/compare/auggie-vs-kilo-code-cli.md)\n- [Claude Code vs Kilo Code CLI](https://www.anchorterminal.com/compare/claude-code-vs-kilo-code-cli.md)\n- [Cline vs Kilo Code CLI](https://www.anchorterminal.com/compare/cline-vs-kilo-code-cli.md)\n- [Crush vs Kilo Code CLI](https://www.anchorterminal.com/compare/crush-vs-kilo-code-cli.md)\n- [Cursor CLI vs Kilo Code CLI](https://www.anchorterminal.com/compare/cursor-cli-vs-kilo-code-cli.md)\n- [DeepSeek Harness (dsh) vs Kilo Code CLI](https://www.anchorterminal.com/compare/deepseek-harness-vs-kilo-code-cli.md)\n- [dsh-superagent (DeepSeek) vs Kilo Code CLI](https://www.anchorterminal.com/compare/deepseek-superagent-vs-kilo-code-cli.md)\n- [Devin vs Kilo Code CLI](https://www.anchorterminal.com/compare/devin-vs-kilo-code-cli.md)\n- [Droid CLI vs Kilo Code CLI](https://www.anchorterminal.com/compare/droid-cli-vs-kilo-code-cli.md)\n- [Pi vs Kilo Code CLI](https://www.anchorterminal.com/compare/earendil-pi-vs-kilo-code-cli.md)\n- [Gemini CLI vs Kilo Code CLI](https://www.anchorterminal.com/compare/gemini-cli-vs-kilo-code-cli.md)\n- [GitHub Copilot CLI vs Kilo Code CLI](https://www.anchorterminal.com/compare/github-copilot-cli-vs-kilo-code-cli.md)\n- [goose vs Kilo Code CLI](https://www.anchorterminal.com/compare/goose-vs-kilo-code-cli.md)\n- [Harness² vs Kilo Code CLI](https://www.anchorterminal.com/compare/harness2-vs-kilo-code-cli.md)\n- [HarnessRouter vs Kilo Code CLI](https://www.anchorterminal.com/compare/harnessrouter-vs-kilo-code-cli.md)\n- [Jules vs Kilo Code CLI](https://www.anchorterminal.com/compare/jules-vs-kilo-code-cli.md)\n- [Junie CLI vs Kilo Code CLI](https://www.anchorterminal.com/compare/junie-vs-kilo-code-cli.md)\n- [Kilo Code CLI vs Kimi Code CLI](https://www.anchorterminal.com/compare/kilo-code-cli-vs-kimi-code-cli.md)\n- [Kilo Code CLI vs Kiro CLI](https://www.anchorterminal.com/compare/kilo-code-cli-vs-kiro-cli.md)\n- [Kilo Code CLI vs mini-swe-agent](https://www.anchorterminal.com/compare/kilo-code-cli-vs-mini-swe-agent.md)\n- [Kilo Code CLI vs MiniMax Code](https://www.anchorterminal.com/compare/kilo-code-cli-vs-minimax-code.md)\n- [Kilo Code CLI vs Mistral Vibe CLI](https://www.anchorterminal.com/compare/kilo-code-cli-vs-mistral-vibe-cli.md)\n- [Kilo Code CLI vs Muse Code](https://www.anchorterminal.com/compare/kilo-code-cli-vs-muse-code.md)\n- [Kilo Code CLI vs OpenAI Codex](https://www.anchorterminal.com/compare/kilo-code-cli-vs-openai-codex.md)\n- [Kilo Code CLI vs OpenCode](https://www.anchorterminal.com/compare/kilo-code-cli-vs-opencode.md)\n- [Kilo Code CLI vs OpenHands](https://www.anchorterminal.com/compare/kilo-code-cli-vs-openhands.md)\n- [Kilo Code CLI vs OpenMausBot](https://www.anchorterminal.com/compare/kilo-code-cli-vs-openmausbot.md)\n- [Kilo Code CLI vs Prime Agent](https://www.anchorterminal.com/compare/kilo-code-cli-vs-prime-agent.md)\n- [Kilo Code CLI vs Qoder CLI](https://www.anchorterminal.com/compare/kilo-code-cli-vs-qoder-cli.md)\n- [Kilo Code CLI vs Qwen Code](https://www.anchorterminal.com/compare/kilo-code-cli-vs-qwen-code.md)\n- [Kilo Code CLI vs Mirror CLI](https://www.anchorterminal.com/compare/kilo-code-cli-vs-reflection-mirror.md)\n- [Kilo Code CLI vs Rovo Dev CLI](https://www.anchorterminal.com/compare/kilo-code-cli-vs-rovo-dev-cli.md)\n- [Kilo Code CLI vs Unstoppable](https://www.anchorterminal.com/compare/kilo-code-cli-vs-unstoppable.md)\n- [Kilo Code CLI vs Vibe-Trading](https://www.anchorterminal.com/compare/kilo-code-cli-vs-vibe-trading.md)\n- [Kilo Code CLI vs Warp (Warp Agent CLI and the Oz Agent API)](https://www.anchorterminal.com/compare/kilo-code-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 Kimi Code CLI](https://www.anchorterminal.com/compare/clawboo-vs-kimi-code-cli.md)\n- [Clawboo vs Kiro CLI](https://www.anchorterminal.com/compare/clawboo-vs-kiro-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 Kilo Code CLI](https://www.anchorterminal.com/compare/cli-manager-vs-kilo-code-cli.md)\n- [Harness vs Kilo Code CLI](https://www.anchorterminal.com/compare/harness-autonomous-vs-kilo-code-cli.md)\n- [Kilo Code CLI vs Paperclip](https://www.anchorterminal.com/compare/kilo-code-cli-vs-paperclip.md)\n- [Kilo Code CLI vs Parallax](https://www.anchorterminal.com/compare/kilo-code-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 Kilo Code CLI", "url": "" } ], "description": "Kilo Code CLI scores 73 (BB) to Clawboo's 61.4 (C) for multi-agent orchestration. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Clawboo C 61.4", "Kilo Code CLI BB 73", "scores" ], "h1": "Clawboo vs Kilo Code CLI", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/clawboo-vs-kilo-code-cli", "published": "2026-10-01", "section": "tools", "title": "Clawboo vs Kilo Code CLI for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-01", "url": "https://www.anchorterminal.com/compare/clawboo-vs-kilo-code-cli" }, "tokens": { "markdown": 6550, "slim": 3330 }, "version": 1 }