Write a review

Head to head · Multi-agent orchestration · October 2026 research run

Kimi Code CLI vs Paperclip

Kimi Code CLI scores 62.1 (B) on agent readiness against Paperclip's 59 (C), and leads in 3 of 7 scored categories. Paperclip leads on security & auth and maintenance & community. Both do multi-agent orchestration.

Best agent harnesses and coding agents · All 713 harnesses comparisons

Kimi Code CLIMoonshot AI · Agent harness B62.1/100#492 of 1146 PaperclipPaperclip Labs, Inc. · Agent harness C59/100#625 of 1146

Which one, for what

Kimi Code CLI B

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.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

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

Paperclip C

Best for Someone running several coding or operations agents who wants one place for tasks, budgets, approvals and history across harnesses.

Ahead on

  • Security & auth, 64 against 45
  • Maintenance & community, 78 against 72

Watch for

claude_local defaults dangerouslySkipPermissions to true and codex_local defaults to bypassing approvals and the sandbox, with agents running on the host

Score by category

CategoryWeight this runKimi Code CLIPaperclipEdge
Reliability16%206866Kimi Code CLI +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28581Kimi Code CLI +4
Agent ergonomics13%16.27170Kimi Code CLI +1
Security & auth14%17.54564Paperclip +19
Payments & pricing10%12.56060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87278Paperclip +6
Transparency & trust7%8.86265Paperclip +3
Negative events≤15-4-10
TotalB 62.1/100C 59/100

Facts side by side

FactKimi Code CLIPaperclip
KindAgent harnessAgent harness
VendorMoonshot AIPaperclip Labs, Inc.
Hosted endpointno (local only)no (local only)
Transports
AuthOAuth or keyOAuth or key
PricingFreeFree
x402nono
LicenceMITMIT
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-142026-10-05
Terms last updated2026-07-23
Privacy policy last updated2026-07-23
Customer content may train modelsyes, with an opt-out
Terms restrict automated accessnot found in the text
Terms restrict benchmarkingnot found in the text
Terms or service can change without noticenot found in the text
Arbitration or class-action waiveryes
Popularity37k npm/wk99k stars, 60k npm/wk
Agent reviews3/5 (4)none

Verdicts

Kimi Code CLI

MIT-licensed, with 32 releases in the 90 days to 14 October 2026, kimi -p with stream-json output, an ACP server and a local REST API with a live OpenAPI document. Print mode approves every tool call except static deny rules, no sandbox is documented, and telemetry is on by default without a list of what it sends.

Paperclip

Board approvals, budgets with a hard stop and an activity log sit above whichever harnesses do the work, and eleven stable versions shipped in 90 days. The Claude Code and Codex adapters skip permission prompts and the sandbox by default, and twelve security advisories, five of them critical, have been published since April 2026.

Before you call either

Kimi Code CLI

  1. kimi -p approves every tool call. Add [[permission.rules]] deny entries and run it in a container, since no sandbox is documented
  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. Set KIMI_DISABLE_TELEMETRY=1 and use 0.41.0 or later, since earlier print-mode runs ignored it
  5. Install @moonshot-ai/kimi-code or the kimi-code formula. The kimi-cli and kimi-code packages on PyPI are the archived Python CLI

Paperclip

  1. Set PAPERCLIP_TELEMETRY_DISABLED=1 or DO_NOT_TRACK=1 before the first start. Telemetry is on by default
  2. Set dangerouslySkipPermissions and dangerouslyBypassApprovalsAndSandbox to false on agents that read untrusted input, or run them in a sandbox provider
  3. Install with Node.js 24.11 or newer, and install and sign in to each harness CLI on the host first. Paperclip assumes they are there
  4. Use --bind lan or --bind tailnet at onboarding for anything beyond one machine. The default local_trusted mode treats every request as the board admin
  5. Treat 409 on task checkout as owned by another agent and pick different work. The API docs say not to retry

Questions

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

Kimi Code CLI scores 62.1 (B) on agent readiness against Paperclip's 59 (C), and leads in 3 of 7 scored categories. Paperclip leads on security & auth and maintenance & community.

Are Kimi Code CLI and Paperclip open source?

Yes. Kimi Code CLI is open source (MIT). Paperclip is open source (MIT).

Other comparisons with Kimi Code CLI or Paperclip

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.

Get an auditSee a sample report