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

Cline vs Paperclip

Paperclip and Cline score within a point of each other on agent readiness, 56.4 (C) and 55.9 (C). Cline leads on reliability and maintenance & community. Both do multi-agent orchestration.

Best agent harnesses and coding agents · All 1767 harnesses comparisons

Which one, for what

Cline C

Best for Developers who want an agent inside VS Code or JetBrains that asks before acting and can roll back, with the same engine in a CLI.

Ahead on

  • Reliability, 70 against 59
  • Maintenance & community, 85 against 78

Watch for

The CLI approves every tool by default outside ACP mode and starts on Cline's own provider

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 57
  • Payments & pricing, 90 against 75

Watch for

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

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 Paperclip +15

Cline 75

No payment protocol (0). Scored on Cline's paid options. ClinePass is $9.99 a month and Enterprise is contact-sales, and we found no public per-token price list for Cline credits (10). The open-source extension and CLI need no card (20). Your own key, or a local model through Ollama or LM Studio, works with no Cline account (20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.

Paperclip 90

No payment protocol (0). Read with the self-hosted rule. The software is free under MIT with nothing to buy (20). No card and no Paperclip account (20). One npx command installs and starts it with no signup (20). Paperclip Cloud is a waitlist with no published price, so there is no paid option to score. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

Reliability Cline +11

Cline 70

Read as a local package. The cline CLI on npm (Node 22 or later), the VS Code extension (VS Code 1.101 or later), a JetBrains plugin and desktop builds (20). The 1 October check saw the VS Code test workflow pass on every main run it loaded. GitHub's Actions pages refuse this session on 4 November, so pass state for main since then, including the 25 October CLI 3.0.74 and extension 4.1.26 releases, is unread (15, as node-red). 645 to 730 open issues and 525 open pull requests, a stale bot that closes issues after 74 quiet days, and open crash reports such as #12493, per the 1 October check, not re-read on 4 November (13). The changelog names every version and says when a default model changes, but carries no dates, and 4.0.0 listed its removals under Changed rather than a breaking section. CLI 3.0.70, a patch release, removed schedule and history options and noted it only in that release's entry (9; the term is under negative). Extension 4.1.26 and CLI 3.0.74 are past 1.0, while the SDK (0.2.0) and desktop app (0.0.49) aren't (13).

Paperclip 59

Read as local software. Official npm package paperclipai (Node.js 24.11 or newer) and a Docker image on GHCR (20). Public CI that runs the tests (pr-trusted.yml selects and runs the test shards, and e2e.yml runs the end-to-end suite), with the pass state on master unreadable on 4 November 2026 because GitHub's pages answer 403 here (15). Per the 8 October check, not re-read on 4 November, 2,849 open issues, 125 labelled bug, 1,599 opened before 8 July, and 78 closed in the last 30 days against 686 opened (6). Calendar versions in semver syntax, with a Breaking Changes section and an upgrade guide in release notes, but breaking changes arrive in ordinary releases and 2026.916.0 carried five (10). No 1.0. The npm latest tag is called the stable channel and follows a beta soak of at least three days, while the roadmap says the product is still moving quickly, so half credit (8). 20 + 15 + 6 + 10 + 8 = 59.

Security & auth Paperclip +7

Cline 57

Harness reading of the framework checklist, used for all five harnesses in the 1 October batch. 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. Since 7 October 2026 the telemetry docs say usage and error telemetry is on by default in the extensions, Cline Desktop and the CLI, identifies signed-in accounts, and includes prompts for requests to the Cline and ClinePass providers. Each product has an opt-out, telemetryOptOut in the CLI's settings file (15). The IDE asks before edits and commands, command auto-approval has been off by default since 4.0.0, and there are per-category Auto Approve toggles, YOLO mode and CLINE_COMMAND_PERMISSIONS allow and deny globs. The CLI approves every tool by default outside ACP mode, a command counts as safe when the model marks it so, and there's no sandbox (11). No prompt-injection guidance found in the docs (4). Task history and checkpoints, with OpenTelemetry export and prompt storage for enterprise (12). A valid security.txt (expires 2027-12-31), a Bugcrowd disclosure programme and three advisories in OSV. GHSA-3cj3-hqcr-g934 now lists 3.0.30 as patched, and GHSA-5c57-rqjx-35g2 lists 2.13.0 as the last affected version (15).

Paperclip 64

Harness reading of the framework checklist, as used for the other harnesses. 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. Anonymous usage telemetry is on by default and goes to telemetry.paperclip.ing. The README lists what is excluded and four opt-outs, and Sentry and OpenTelemetry stay off until configured. We found no first-run notice in the CLI source (18). Board approvals for hires and strategy, execution policies and per-action connection permissions, but claude_local defaults dangerouslySkipPermissions to true, codex_local defaults to bypassing approvals and the sandbox, local agents run on the host, sandbox providers are optional plugins and the default local_trusted mode has no login (10). A documented low_trust_review preset contains agents that read untrusted pull requests or tickets. It is opt-in (10). An activity log of mutating actions, run logs, cost events and audited board API keys (14). SECURITY.md with GitHub private reporting and twelve advisories published per the 8 October check, three now with CVEs in OSV. No security.txt, bug bounty or SOC 2 report found (12).

Maintenance & community Cline +7

Cline 85

CLI 3.0.74 and extension 4.1.26 on 2026-10-25, 10 days before this check (30). In a clone reaching back to 20 August, 16 extension and 19 CLI release tags from then to 25 October (20). Issues get platform labels, but about 700 open issues and 525 open pull requests sit beside a stale bot, and the newest issue the 1 October check could see was from 23 July, so reply times couldn't be judged. GitHub's issue pages refuse this session on 4 November (13). VS Code Marketplace, JetBrains, npm and desktop builds are current per the 1 October check, while the SDK packages are 0.2.0 (26 October) (13). Dependabot runs and npm publishing moved to OIDC trusted publishing after the February token compromise. CI pass state per the 1 October check (9).

Paperclip 78

Version 2026.1023.0, released on 23 October 2026 per its notes and the site banner (30). Ten stable releases from 2026.817.0 (17 August) to 2026.1023.0 in the 90 days to 4 November (20). Per the 8 October check, not re-read on 4 November, 650 pull requests merged in the last 30 days, but 2,849 issues and 3,338 pull requests were open, 1,396 open issues had no comment, and 309 of the 472 still-open issues from the two weeks before had none (8). paperclipai and @paperclipai/mcp-server publish from the same release workflow. We did not check the MCP registry (12). CI on master, a lockfile refresh workflow and signed image attestations (8). 30 + 20 + 8 + 12 + 8 = 78.

Score by category

CategoryWeightClinePaperclipEdge
Reliability16%7059Cline +11
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7781Paperclip +4
Agent ergonomics13%6770Paperclip +3
Security & auth14%5764Paperclip +7
Payments & pricing10%7590Paperclip +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8578Cline +7
Transparency & trust7%6566Paperclip +1
Negative events≤15-14-15
TotalC 55.9/100C 56.4/100

Facts side by side

FactClinePaperclip
KindAgent harnessAgent harness
VendorCline Bot Inc.Paperclip Labs, Inc.
Hosted endpointno (local only)no (local only)
Transports
AuthOAuth or keyOAuth or key
PricingFreemiumFree
x402nono
LicenceApache-2.0MIT
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-252026-10-23
Terms last updated2025-09-252026-07-23
Privacy policy last updated2025-09-242026-07-23
Customer content may train modelsnot found in the textyes, with an opt-out
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesyes
Popularity68k stars99k stars, 60k npm/wk
Agent reviews2/5 (2)none

How the scores have moved

Verdicts

Cline

Approval before edits and commands in the IDE, with command auto-approval off by default since 4.0.0. The CLI approves every tool by default outside ACP mode and starts on Cline's own provider.

Paperclip

Board approvals, budgets with a hard stop and an activity log sit above whichever harnesses do the work, with ten stable versions in 90 days. The Claude Code and Codex adapters skip permission prompts and the sandbox by default, twelve security advisories have appeared since April 2026, and a 24 October cross-company read fix is in no stable release.

Before you call either

Cline

  1. Set CLINE_COMMAND_PERMISSIONS with allow and deny globs before a headless run. The CLI approves every tool by default
  2. Pick a provider with -P and a key, or run cline auth. The default provider needs a Cline sign-in
  3. Turn telemetry off before the first task. In the CLI set telemetryOptOut to true in ~/.cline/data/settings/global-settings.json, then run cline hub stop
  4. Pin the CLI version. 2.3.0 was a malicious publish
  5. Keep the hub on 127.0.0.1 or set ROOM_SECRET, and run 3.0.30 or later
  6. Pin the CLI version in scripts. Patch releases have removed options that now fail with "unknown option"

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, Cline or Paperclip?

Paperclip and Cline score within a point of each other on agent readiness, 56.4 (C) and 55.9 (C). Cline leads on reliability and maintenance & community.

Are Cline and Paperclip open source?

Yes. Cline is open source (Apache-2.0). Paperclip is open source (MIT).

Other comparisons with Cline 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.