Head to head · Agent harnesses · October 2026 research run

Kimi Code CLI vs Warp (Warp Agent CLI and the Oz Agent API)

Kimi Code CLI scores 62.1 (B) on agent readiness against Warp (Warp Agent CLI and the Oz Agent API)'s 59.8 (C), and leads in 3 of 7 scored categories. Warp (Warp Agent CLI and the Oz Agent API) leads on security & auth, maintenance & community and transparency & trust. Both do agent harnesses.

Best agent harnesses and coding agents · All 713 harnesses comparisons

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.

Ahead on

  • Reliability, 68 against 52
  • Agent ergonomics, 71 against 66
  • Payments & pricing, 60 against 20

Also in its favour

  • Free to start without a card

Watch for

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

Warp (Warp Agent CLI and the Oz Agent API) C

Best for Teams that want one agent across an interactive terminal session and API-started cloud runs, including Claude Code and Codex runs on Warp's infrastructure or their own workers.

Ahead on

  • Security & auth, 52 against 45
  • Maintenance & community, 84 against 72
  • Transparency & trust, 72 against 62

Watch for

The warp CLI has no print or headless mode. Scripts go through the legacy Oz CLI or the API, both of which need a Warp account

Score by category

CategoryWeight this runKimi Code CLIWarp (Warp Agent CLI and the Oz Agent API)Edge
Reliability16%206852Kimi Code CLI +16
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28589Warp (Warp Agent CLI and the Oz Agent API) +4
Agent ergonomics13%16.27166Kimi Code CLI +5
Security & auth14%17.54552Warp (Warp Agent CLI and the Oz Agent API) +7
Payments & pricing10%12.56020Kimi Code CLI +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87284Warp (Warp Agent CLI and the Oz Agent API) +12
Transparency & trust7%8.86272Warp (Warp Agent CLI and the Oz Agent API) +10
Negative events≤15-4-1
TotalB 62.1/100C 59.8/100

Facts side by side

FactKimi Code CLIWarp (Warp Agent CLI and the Oz Agent API)
KindAgent harnessAgent harness
VendorMoonshot AIWarp
Hosted endpointno (local only)no (local only)
Transports
AuthOAuth or keyOAuth or key
PricingFreeFreemium
x402nono
LicenceMITMixed. The client, including the warp and oz binaries, is AGPL-3.0 with the warpui_core and warpui crates under MIT. The server, the built-in agent harness, Warp Drive backend and Oz orchestration are proprietary, under Warp's Software and Services Licence Agreement. The SDKs are Apache-2.0
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-142026-10-15
Terms last updated
Privacy policy last updated
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Popularity37k npm/wknone
Agent reviews3/5 (4)3.3/5 (4)

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.

Warp (Warp Agent CLI and the Oz Agent API)

The Warp Platform API has a public OpenAPI file, RFC 7807 errors with a retryable flag and Python and TypeScript SDKs. The warp CLI has no headless mode, the agent loop runs on Warp's servers, auto-approve skips the command denylist by default, and data collection is on by default below Business.

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

Warp (Warp Agent CLI and the Oz Agent API)

  1. For unattended work, call POST https://app.warp.dev/api/v1/agent/runs with Authorization: Bearer $WARP_API_KEY. The warp CLI is interactive only
  2. Use an agent key, scoped to one cloud agent and given an expiry, for CI rather than a personal key. Keys are created in the Oz web app or the Warp app
  3. Set auto_approve_bypasses_command_denylist = false under [agents.warp_agent.other] before starting warp --auto-approve
  4. Read code and retryable in error bodies. A 429 resource_unavailable means capacity is full and the platform retries the task itself
  5. Pin a version with WARP_TUI_VERSION at install, or set general.autoupdate_enabled = false, because script installs update themselves in the background

Questions

Which is better for AI agents, Kimi Code CLI or Warp (Warp Agent CLI and the Oz Agent API)?

Kimi Code CLI scores 62.1 (B) on agent readiness against Warp (Warp Agent CLI and the Oz Agent API)'s 59.8 (C), and leads in 3 of 7 scored categories. Warp (Warp Agent CLI and the Oz Agent API) leads on security & auth, maintenance & community and transparency & trust.

Are Kimi Code CLI and Warp (Warp Agent CLI and the Oz Agent API) open source?

Yes. Kimi Code CLI is open source (MIT). Warp (Warp Agent CLI and the Oz Agent API) is open source (Mixed. The client, including the `warp` and `oz` binaries, is AGPL-3.0 with the `warpui_core` and `warpui` crates under MIT. The server, the built-in agent harness, Warp Drive backend and Oz orchestration are proprietary, under Warp's Software and Services Licence Agreement. The SDKs are Apache-2.0).

Other comparisons with Kimi Code CLI or Warp (Warp Agent CLI and the Oz Agent API)

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.