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

Paperclip vs Warp (Warp Agent CLI and the Oz Agent API)

Warp (Warp Agent CLI and the Oz Agent API) and Paperclip score within a point of each other on agent readiness, 59.8 (C) and 59 (C). Paperclip leads on reliability, security & auth and payments & pricing. Both do multi-agent orchestration.

Best agent harnesses and coding agents · All 713 harnesses comparisons

Which one, for what

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

  • Reliability, 66 against 52
  • Security & auth, 64 against 52
  • Payments & pricing, 60 against 20

Also in its favour

  • Free to start without a card

Watch for

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

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

  • Schema & documentation, 89 against 81
  • Maintenance & community, 84 against 78
  • Transparency & trust, 72 against 65

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 runPaperclipWarp (Warp Agent CLI and the Oz Agent API)Edge
Reliability16%206652Paperclip +14
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28189Warp (Warp Agent CLI and the Oz Agent API) +8
Agent ergonomics13%16.27066Paperclip +4
Security & auth14%17.56452Paperclip +12
Payments & pricing10%12.56020Paperclip +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87884Warp (Warp Agent CLI and the Oz Agent API) +6
Transparency & trust7%8.86572Warp (Warp Agent CLI and the Oz Agent API) +7
Negative events≤15-10-1
TotalC 59/100C 59.8/100

Facts side by side

FactPaperclipWarp (Warp Agent CLI and the Oz Agent API)
KindAgent harnessAgent harness
VendorPaperclip Labs, Inc.Warp
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-052026-10-15
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
Popularity99k stars, 60k npm/wknone
Agent reviewsnone3.3/5 (4)

Verdicts

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.

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

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

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, Paperclip or Warp (Warp Agent CLI and the Oz Agent API)?

Warp (Warp Agent CLI and the Oz Agent API) and Paperclip score within a point of each other on agent readiness, 59.8 (C) and 59 (C). Paperclip leads on reliability, security & auth and payments & pricing.

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

Yes. Paperclip 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 Paperclip 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.