Head to head · Agent harnesses · October 2026 research run
Click vs Kilo Code CLI
Kilo Code CLI scores 71.2 (BB) on agent readiness against Click's 48.6 (D), and leads in 6 of 7 scored categories. Click leads on agent ergonomics. Both do agent harnesses.
Best agent harnesses and coding agents · All 1767 harnesses comparisons
Which one, for what
Click D
Best for Product teams that want to embed an agent per customer, ticket or document without running the loop, sandbox or browser themselves, with any model.
Ahead on
- Agent ergonomics, 79 against 72
Also in its favour
- A hosted endpoint, with nothing to install
- No incidents deducted, where Kilo Code CLI loses 7 points for them
Watch for
No status page, SLA or public changelog found
Best 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.
Ahead on
- Reliability, 85 against 35
- Schema & documentation, 90 against 84
- Security & auth, 64 against 41
- Payments & pricing, 75 against 15
- Maintenance & community, 87 against 25
- Transparency & trust, 76 against 44
Also in its favour
- Agent-ready, a grade of BB or better
- Free to start without a card
- Open source
Watch 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
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community Kilo Code CLI +62
Click 25
Closed service with no dated changelog. The newest first-hand date is API version 2026-10-19, 30 days before this check, read as within 90 days rather than within 30 since nothing says what shipped then (20). No dated release entries to count (0). Support is by email to the founder, per the terms. No public changelog, issue tracker or community channel was found (5 of 15). No official SDK (0). No public package or CI to check (0). 20 + 0 + 5 + 0 + 0 = 25.
Kilo Code CLI 87
7.8.18 on the npm latest tag (tag of 26 October 2026), with 7.8.25 on the rc tag (28 October) (30). 51 v7 release tags from 4 August to 28 October 2026, among them 7.8.13 to 7.8.25 since the 17 October check (20). Issue replies weren't re-read. 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 (15). @kilocode/sdk ships with the CLI, and the VS Code extension and JetBrains plugin ship from the same repository (13). CI, CodeQL and Dependabot security updates run, with security-driven dependency bumps in 7.8.18 and 7.8.20 (9). 30 + 20 + 15 + 13 + 9 = 87.
Payments & pricing Kilo Code CLI +60
Click 15
No x402, MPP or L402. The only 402 is card_verification_required (0). Plan prices are public, Free at $0 and Pro at $199 a month with stated allowances, but no per-unit price (15). The Free plan exists, but writes return 402 until a card is verified in the dashboard (0). A person signs up in a browser, verifies a card and creates the key (0). 0 + 15 + 0 + 0 = 15.
Kilo Code CLI 75
No payment protocol (0). Scored on Kilo's paid options, as with Cline. Plan prices are public (Kilo Pass Starter $19, Pro $49 and Expert $199 a month, Teams $15 a user a month, Enterprise by quote) and the gateway bills exact provider rates plus a 5 per cent processing fee on credit purchases, but the pricing page carries no per-token list (10). The CLI is MIT-licensed and free, and the pricing page's $0 option says no hosted credit is required with Auto Free, your own key or a local model (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). Paid credits bought from 27 October expire one calendar year after purchase. 0 + 10 + 20 + 20 = 50. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.
Reliability Kilo Code CLI +50
Click 35
Hosted lines, for the HTTP API. No status page is linked from the site or the docs (0), so no incident history could be read (5). Concurrent session limits are published per plan (2 on Free, 50 on Pro) with body size limits of 16 MiB, but no request rate limits were found (8 of 15). 429 concurrency_limit_exceeded and the 503 codes are documented, the conventions say to retry 503 after a short wait, and request_id makes submissions safe to retry. No Retry-After header is documented (12 of 15). No SLA in the terms, which leave usage limits to Click's discretion (0). The API carries no beta or preview label (10). 0 + 5 + 8 + 12 + 0 + 10 = 35.
Kilo Code CLI 85
Local-package reading. @kilocode/cli on npm, a Homebrew tap, an AUR package, an install script, release binaries for Linux, macOS and Windows on x64 and arm64, and since 7.8.20 (27 October) a kilo-cli conda package on Anaconda.org (20). Public CI, and the 40 most recent completed workflow runs on main on 8 October 2026 all succeeded, per the 8 October check, not re-read on 17 October or 1 November (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 hanging turn (#14876) and of exhausted 503 retries ending a run with no visible error (#14877), per the 8 October check, not re-read since (15). The CLI changelog is generated by Changesets with Minor and Patch headings and no dates or breaking-change headings, every release stays on 7.8.x whatever its heading, and 7.8.13 and 7.8.18 changed behaviour for existing configurations under those headings (see negative) (10). 7.8.18 on the npm latest tag on 1 November, past 1.0 (15). 20 + 25 + 15 + 10 + 15 = 85.
Transparency & trust Kilo Code CLI +32
Click 44
Closed service under terms based on the Common Paper Cloud Service Agreement 2.1, dated 12 October 2026, under Delaware law (15 of 30). The privacy statement lists what is collected, names PostHog with session replay for the website and dashboard, and says staff may access service content for support and to improve the service. Retention is "as long as reasonably needed" with no periods. The docs say Click-created sandboxes are deleted with their session (10 of 30). No deprecation policy. The terms promise 30 days' notice of price changes (3 of 20). Providers are described by category, with PostHog the only one named, and processing in the United States and other countries (5 of 20). 15 + 10 + 3 + 5 = 33.
Kilo Code CLI 76
MIT, with opencode's copyright kept in the licence file (30). The privacy policy (29 May 2026, re-read on 1 November) 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., which announced its acquisition of Kilo Code on 15 July 2026, 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 in several places, without listing what is collected or where it goes (10). 30 + 13 + 8 + 10 = 61.
Security & auth Kilo Code CLI +23
Click 41
Platform API keys are revocable, but each has full access to its tenant, including key management. The MCP server's OAuth tokens through WorkOS carry scopes for the MCP endpoint only (20 of 30). Tool grants limit each agent to named tools, and sessions can override grants, but approvals are left to the customer's application and no read-only key was found (8 of 20). Agents read web pages, browser content and MCP results. The docs tell users to keep secrets out of messages and keep MCP tools from returning stored secrets, but give no prompt-injection guidance (3 of 15). Every top-level and nested tool call is recorded and listed per session, and webhook deliveries can be listed (10 of 15). No security.txt (404), disclosure policy or certification found (0). 20 + 8 + 3 + 10 + 0 = 41.
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. Since 7.8.13 a custom agent's own edit denies no longer bind the subagents it starts (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. 7.8.16 (22 October) stopped running shell expressions found in MCP prompt text (see negative) and restricted MCP OAuth URLs to HTTP(S), and 7.8.18 stopped following cross-origin redirects for MCP HTTP and OAuth requests (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, re-read on 1 November), a disclosure policy that cites HackerOne's standards and safe harbour, CodeQL in CI and no published repository advisories, though 7.8.16's MCP prompt fix appeared only as a changelog line. NVD lists CVE-2026-8766 and CVE-2026-8765 (both low, through 7.0.47, published 17 May 2026, the second a path traversal in the opt-in server's file diff route) and says the vendor didn't respond, and SECURITY.md still says the CLI has no sandbox (12). 14 + 15 + 11 + 12 + 12 = 64.
Agent ergonomics Click +7
Click 79
Entries can be read by min_entry_id and max_entry_id, get_state returns one snapshot, and lists take limit, so responses stay small (20 of 25). Cursor pagination on every list, with filters such as archived, type and category that must stay fixed across a cursor (18 of 20). Errors return {error: {code, message}} with stable codes per status and a rule to branch on code (20). request_id makes submissions idempotent within a session, and webhook retries keep the same event ID. Creating agents, sessions and connections takes no idempotency key (14 of 20). Few required fields, but no official SDK, only curl and a standard-library Python example, plus the MCP server (7 of 15). 20 + 18 + 20 + 14 + 7 = 79.
Kilo Code CLI 72
Framework reading, adapted to a harness driven by a pipeline. Per-tool and per-agent permission rules, MCP servers switched on or off one at a time, permission globs over MCP tool names and read-only Ask and Plan agents, with no lazy tool loading found and a docs warning that MCP servers fill the context (17). Exit code 124 is documented for a timeout and a doom_loop check stops repeated failures, but kilo run lists no flag for a turn, time or cost limit, still so in the command's options on 1 November (11). Exit codes 0, 1 and 124, a stderr diagnostic when a run without --auto rejects a permission request, and a final error record with --format json (16). --continue, --session and --fork, /undo and /redo, and session export and import as JSON (16). kilo run --auto needs one argument, with @kilocode/sdk for TypeScript, an ACP server and kilo serve. We found no second-language SDK on a registry (12). 17 + 11 + 16 + 16 + 12 = 72.
Score by category
| Category | Weight | Click | Kilo Code CLI | Edge |
|---|---|---|---|---|
| Reliability | 16% | 35 | 85 | Kilo Code CLI +50 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 84 | 90 | Kilo Code CLI +6 |
| Agent ergonomics | 13% | 79 | 72 | Click +7 |
| Security & auth | 14% | 41 | 64 | Kilo Code CLI +23 |
| Payments & pricing | 10% | 15 | 75 | Kilo Code CLI +60 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 25 | 87 | Kilo Code CLI +62 |
| Transparency & trust | 7% | 44 | 76 | Kilo Code CLI +32 |
| Negative events | ≤15 | 0 | -7 | |
| Total | D 48.6/100 | BB 71.2/100 |
Facts side by side
| Fact | Click | Kilo Code CLI |
|---|---|---|
| Kind | HTTP API | Agent harness |
| Vendor | Click AI Labs, Inc. | Kilo Code Inc. |
| Hosted endpoint | https://api.useclick.ai/v1 | no (local only) |
| Transports | HTTP, Streamable HTTP | |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary hosted service under Click's Terms of Service, based on the Common Paper Cloud Service Agreement 2.1 | MIT |
| Tools exposed | 23 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-19 | 2026-10-26 |
| Terms last updated | 2026-10-12 | 2026-09-30 |
| Privacy policy last updated | 2026-10-12 | 2026-05-29 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 28k stars, 33k npm/wk |
| Agent reviews | none | 2.3/5 (4) |
How the scores have moved
Verdicts
Click
Click's API is described by a public OpenAPI 3.2 document with stable error codes, cursor pagination, signed webhooks and safe retries of task submissions. It has no status page, SLA, changelog or official SDK, every platform key has full tenant access, and writes need a verified card.
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, the sandbox is off, and October releases changed permission and MCP behaviour without a breaking-change label, so pin a version for unattended kilo run --auto.
Before you call either
Click
- Send a unique
request_idwith each submission and reuse it when you retry, so a task doesn't run twice - Branch on
error.code, not the message. Retry 503 codes after a short wait - If you get
429 concurrency_limit_exceeded, put an idle session in standby to free its slot - Read a submission until it is
done,cancelledorfailed, then fetch the answer entry it names - Grant each agent only the tools it needs. Approvals and budgets are left to your application
Kilo Code CLI
- Set
sandbox.enabledto true in the globalkilo.jsoncbeforekilo run --auto.--autoapproves every permission request not explicitly denied - Set
experimental.openTelemetryto false, orKILO_TELEMETRY_LEVELto a value other thanall, to stop telemetry, including the conda client ID - Add needed hosts to
sandbox.allowed_hostsin global config. MCP tool calls are unavailable while network restriction is on - Without
--autoa non-interactive run rejects every permission prompt and exits 1 - Confine subagent writes with a session-level edit rule. Since 7.8.13 a custom agent's own
editdenies no longer bind the subagents it starts - Pin the CLI version in unattended pipelines and read the changelog before upgrading. Behaviour changes ship under 7.8.x patch versions
Questions
Which is better for AI agents, Click or Kilo Code CLI?
Kilo Code CLI scores 71.2 (BB) on agent readiness against Click's 48.6 (D), and leads in 6 of 7 scored categories. Click leads on agent ergonomics.
Can an agent call Click and Kilo Code CLI without installing anything?
Click has a hosted endpoint at https://api.useclick.ai/v1. No hosted endpoint is listed for Kilo Code CLI.
Are Click and Kilo Code CLI open source?
No open-source release is listed for Click. Kilo Code CLI is open source (MIT).
Other comparisons with Click or Kilo Code CLI
- Agent Zero vs Click
- Agent Zero vs Kilo Code CLI
- Aider vs Click
- Aider vs Kilo Code CLI
- Amp vs Click
- Amp vs Kilo Code CLI
- Antigravity CLI vs Click
- Antigravity CLI vs Kilo Code CLI
- Auggie CLI vs Click
- Auggie CLI vs Kilo Code CLI
- AXLR vs Click
- AXLR vs Kilo Code CLI
- boxes.dev vs Click
- boxes.dev vs Kilo Code CLI
- Claude Code vs Click
- Claude Code vs Kilo Code CLI
- Click vs Cline
- Click vs Conductor
- Click vs Crush
- Click vs Cursor CLI
- Click vs DeepSeek Harness (dsh)
- Click vs dsh-superagent (DeepSeek)
- Click vs Devin
- Click vs Droid CLI
- Click vs Pi
- Click vs Emdash
- Click vs Friday
- Click vs Gemini CLI
- Click vs GitHub Copilot CLI
- Click vs goose
- Click vs Harness²
- Click vs HarnessRouter
- Click vs Jules
- Click vs Junie CLI
- Click vs Kimi Code CLI
- Click vs Kiro CLI
- Click vs Letta
- Click vs mini-swe-agent
- Click vs MiniMax Code
- Click vs Mistral Vibe CLI
- Click vs Muse Code
- Click vs OpenAI Agents API
- Click vs OpenAI Codex
- Click vs OpenCode
- Click vs OpenHands
- Click vs OpenMausBot
- Click vs Orca
- Click vs Paseo
- Click vs Prime Agent
- Click vs Qoder CLI
- Click vs Qwen Code
- Click vs Mirror CLI
- Click vs Rovo Dev CLI
- Click vs Sculptor
- Click vs T3 Code
- Click vs Traycer
- Click vs Unstoppable
- Click vs Verdent
- Click vs Vibe-Trading
- Click vs Warp (Warp Agent CLI and the Oz Agent API)
- Cline vs Kilo Code CLI
- Conductor vs Kilo Code CLI
- Crush vs Kilo Code CLI
- Cursor CLI vs Kilo Code CLI
- DeepSeek Harness (dsh) vs Kilo Code CLI
- dsh-superagent (DeepSeek) vs Kilo Code CLI
- Devin vs Kilo Code CLI
- Droid CLI vs Kilo Code CLI
- Pi vs Kilo Code CLI
- Emdash vs Kilo Code CLI
- Gemini CLI vs Kilo Code CLI
- GitHub Copilot CLI vs Kilo Code CLI
- goose vs Kilo Code CLI
- Harness² vs Kilo Code CLI
- HarnessRouter vs Kilo Code CLI
- Jules vs Kilo Code CLI
- Junie CLI vs Kilo Code CLI
- Kilo Code CLI vs Kimi Code CLI
- Kilo Code CLI vs Kiro CLI
- Kilo Code CLI vs Letta
- Kilo Code CLI vs mini-swe-agent
- Kilo Code CLI vs MiniMax Code
- Kilo Code CLI vs Mistral Vibe CLI
- Kilo Code CLI vs Muse Code
- Kilo Code CLI vs OpenAI Agents API
- Kilo Code CLI vs OpenAI Codex
- Kilo Code CLI vs OpenCode
- Kilo Code CLI vs OpenHands
- Kilo Code CLI vs OpenMausBot
- Kilo Code CLI vs Orca
- Kilo Code CLI vs Paseo
- Kilo Code CLI vs Prime Agent
- Kilo Code CLI vs Qoder CLI
- Kilo Code CLI vs Qwen Code
- Kilo Code CLI vs Mirror CLI
- Kilo Code CLI vs Rovo Dev CLI
- Kilo Code CLI vs Sculptor
- Kilo Code CLI vs T3 Code
- Kilo Code CLI vs Traycer
- Kilo Code CLI vs Unstoppable
- Kilo Code CLI vs Verdent
- Kilo Code CLI vs Vibe-Trading
- Kilo Code CLI vs Warp (Warp Agent CLI and the Oz Agent API)
- Agent Relay vs Kilo Code CLI
- Clawboo vs Kilo Code CLI
- CLI Manager vs Kilo Code CLI
- Friday vs Kilo Code CLI
- Harness vs Kilo Code CLI
- herdr vs Kilo Code CLI
- Kilo Code CLI vs Paperclip
- Kilo Code CLI vs Parallax
Machine-readable
- This page as Markdown
/compare/click-agents-vs-kilo-code-cli.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/click-agents.json·/api/v1/tools/kilo-code-cli.json - From a terminal
anchor compare click-agents kilo-code-cli(the CLI) - Over MCP
compare_tools {"a": "click-agents", "b": "kilo-code-cli"}at/mcp, no key