Head to head · Agent harnesses · October 2026 research run

Click vs Kimi Code CLI

Kimi Code CLI scores 61.8 (C) 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 71

Also in its favour

  • A hosted endpoint, with nothing to install
  • No incidents deducted, where Kimi Code CLI loses 8 points for them

Watch for

No status page, SLA or public changelog found

Kimi Code CLI C

Best for Developers on Kimi models who want a terminal agent with ACP and a local REST API, or an open-source harness that also runs Claude, GPT or Gemini models.

Ahead on

  • Reliability, 68 against 35
  • Payments & pricing, 90 against 15
  • Maintenance & community, 72 against 25
  • Transparency & trust, 62 against 44

Also in its favour

  • Free to start without a card
  • Open source

Watch for

Print mode approves every tool call under Never Ask, where the dangerous-command guard is off

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.

Payments & pricing Kimi Code CLI +75

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.

Kimi Code CLI 90

Self-hosted rule. No payment protocol (0). The CLI is free under MIT with nothing to buy (20). No card or account is needed for the software, and any listed provider's key works (20). An agent can install it from npm and run it with KIMI_MODEL_* variables and no sign-up, given a model key (20). The Kimi Code subscription and Kimi Platform API usage are separate purchases. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

Maintenance & community Kimi Code CLI +47

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.

Kimi Code CLI 72

2.4.1 on 30 October 2026 (30). 30 stable tags from 0.32.0 on 4 August to 2.4.1 on 30 October, plus canary builds since 29 October (20). The 18 October counts from shields.io badges are struck. The clone shows the pace directly, 95 commits from 13 authors between 18 October and 2 November and pull requests numbered past #4600, with the changelog crediting outside contributors in each release. Issue reply times couldn't be read (11). No published SDK. A TypeScript SDK sits in the repository (@moonshot-ai/kimi-code-sdk 0.22.0) marked private, the ACP server and REST API ship inside the CLI, and Homebrew core is current at 2.4.1 (5). CI with a frozen lockfile, lint and a dependency check (sherif), canary and release workflows, no Dependabot or Renovate file, and the pass state unchecked (6). 30 + 20 + 11 + 5 + 6 = 72.

Reliability Kimi Code CLI +33

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.

Kimi Code CLI 68

Local-package reading. An install script that verifies a checksum, npm @moonshot-ai/kimi-code with Node 22.19.0 or newer stated, and Homebrew core at 2.4.1, for macOS, Linux and Windows (20). A public CI workflow runs the build, a smoke test, sharded tests on Linux, tests on Windows, lint and typecheck. GitHub's pages answer 403 in this session, so whether it passes on main wasn't checked (15). The 18 October issue and pull-request counts came from shields.io badges, a third-party copy of GitHub data this run bars, so they are struck. The clone shows 95 commits from 13 authors since 18 October and a changelog that credits merged pull requests up to #4553 in 2.4.1, but which open issues are crashes or regressions, and how fast they're answered, couldn't be read (8). Changesets changelog with Major, Minor and Patch headings and no breaking-change label since 0.28.0. 2.2.0 made executor = "kaos" configs fail validation, 2.3.0 stopped bare-name plugin skill calls and 2.3.2, a patch, removed swarms from kimi -p and ACP (10). 2.4.1, past 1.0 (15). 20 + 15 + 8 + 10 + 15 = 68.

Transparency & trust Kimi Code CLI +18

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.

Kimi Code CLI 62

MIT (30). The docs have no privacy page for the CLI. The Kimi terms (effective 13 August 2026, NOVASCENT PRIVATE LIMITED, Singapore) let Moonshot use content to train its services unless the user opts out by email, prospectively only, and the Kimi privacy policy says content is used for training. The Kimi Platform privacy policy keeps inputs while the account is active. Neither says which applies to CLI sessions (12). The kimi server tree prints a deprecation notice until the next major version, a table names each deprecated config key and the version that replaced it, and the Python Kimi CLI was archived with a migration guide, though its notice gives no date for when old installations stop working (13). Telemetry is documented as on, with a config key and an environment variable to turn it off, but what it collects isn't listed, and print mode ignored the opt-out until 0.41.0 (9).

Agent ergonomics Click +8

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.

Kimi Code CLI 71

Framework reading, adapted to a harness driven by a pipeline. Global tools.enabled and tools.disabled lists, per-agent tool lists, deferred MCP tool loading and a read-only Plan mode (20). stream-json output and a step limit per turn by environment variable, but steps are unlimited by default and there's no wall-time or cost limit for the main turn (13). The server API returns coded envelopes and ACP returns standard JSON-RPC errors, but print mode documents no exit codes outside goal runs (12). Retries only on transient failures and never on an exhausted quota, with --continue, --session, fork, undo and ACP session/load (16). kimi -p needs one argument, with ACP and the REST API as programmatic surfaces but no SDK package in any language (10).

Score by category

CategoryWeightClickKimi Code CLIEdge
Reliability16%3568Kimi Code CLI +33
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8485Kimi Code CLI +1
Agent ergonomics13%7971Click +8
Security & auth14%4145Kimi Code CLI +4
Payments & pricing10%1590Kimi Code CLI +75
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%2572Kimi Code CLI +47
Transparency & trust7%4462Kimi Code CLI +18
Negative events≤150-8
TotalD 48.6/100C 61.8/100

Facts side by side

FactClickKimi Code CLI
KindHTTP APIAgent harness
VendorClick AI Labs, Inc.Moonshot AI
Hosted endpointhttps://api.useclick.ai/v1no (local only)
TransportsHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFree
x402nono
LicenceProprietary hosted service under Click's Terms of Service, based on the Common Paper Cloud Service Agreement 2.1MIT
Tools exposed23none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-192026-10-30
Terms last updated2026-10-122026-08-13
Privacy policy last updated2026-10-122026-08-13
Customer content may train modelsnot found in the textyes, with an opt-out
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularitynone37k npm/wk
Agent reviewsnone3/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.

Kimi Code CLI

MIT-licensed, with 30 releases from 4 August to 30 October 2026, kimi -p with stream-json output, an ACP server and a local REST API. Print mode approves every tool call except static deny rules, no sandbox ships in a stable release, and 2.x minor releases changed behaviour without notice.

Before you call either

Click

  1. Send a unique request_id with each submission and reuse it when you retry, so a task doesn't run twice
  2. Branch on error.code, not the message. Retry 503 codes after a short wait
  3. If you get 429 concurrency_limit_exceeded, put an idle session in standby to free its slot
  4. Read a submission until it is done, cancelled or failed, then fetch the answer entry it names
  5. Grant each agent only the tools it needs. Approvals and budgets are left to your application

Kimi Code CLI

  1. kimi -p approves every tool call. Add [[permission.rules]] deny entries and run it in a container, since no sandbox ships
  2. Set KIMI_LOOP_MAX_STEPS_PER_TURN for unattended runs. Steps per turn are unlimited by default
  3. Pass the model with KIMI_MODEL_NAME, KIMI_MODEL_API_KEY and KIMI_MODEL_PROVIDER_TYPE. OPENAI_API_KEY or ANTHROPIC_API_KEY in the shell is ignored otherwise
  4. Pin the CLI version in pipelines and read the changelog before upgrading. Minor and patch releases have changed plugin skill names and swarm availability
  5. Set KIMI_DISABLE_TELEMETRY=1 and use 0.41.0 or later, since earlier print-mode runs ignored it

Questions

Which is better for AI agents, Click or Kimi Code CLI?

Kimi Code CLI scores 61.8 (C) 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 Kimi Code CLI without installing anything?

Click has a hosted endpoint at https://api.useclick.ai/v1. No hosted endpoint is listed for Kimi Code CLI.

Are Click and Kimi Code CLI open source?

No open-source release is listed for Click. Kimi Code CLI is open source (MIT).

Other comparisons with Click or Kimi Code CLI

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.