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

Paperclip vs Vibe-Trading

Vibe-Trading scores 62.2 (B) on agent readiness against Paperclip's 59 (C), and leads in 2 of 7 scored categories. Paperclip leads on schema & documentation and transparency & trust. Both do multi-agent orchestration.

Best agent harnesses and coding agents · All 792 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

  • Schema & documentation, 81 against 72
  • Transparency & trust, 65 against 47

Watch for

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

Vibe-Trading B

Best for A person or a pipeline that wants a ready-made finance research agent over free market data, with backtests, swarm reviews and exports, run on their own machine or used as an MCP server by another agent.

Ahead on

  • Security & auth, 70 against 64

Also in its favour

  • No key needed to call it
  • Runs on your own machine

Watch for

Three advisories published 2 October 2026 cover 0.1.0 to 0.1.6, two critical, among them unauthenticated API access with an RCE chain

Score by category

CategoryWeight this runPaperclipVibe-TradingEdge
Reliability16%206663Paperclip +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28172Paperclip +9
Agent ergonomics13%16.27067Paperclip +3
Security & auth14%17.56470Vibe-Trading +6
Payments & pricing10%12.56060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87882Vibe-Trading +4
Transparency & trust7%8.86547Paperclip +18
Negative events≤15-10-4
TotalC 59/100B 62.2/100

Facts side by side

FactPaperclipVibe-Trading
KindAgent harnessAgent harness
VendorPaperclip Labs, Inc.HKUDS
Hosted endpointno (local only)no (local only)
Transportsstdio, Streamable HTTP, SSE (legacy)
AuthOAuth or keyNone
PricingFreeFree
x402nono
LicenceMITMIT
Tools exposednone82
Read-only variant documentednono
llms.txtyesno
Last release2026-10-052026-10-21
Terms last updated2026-07-23no document linked
Privacy policy last updated2026-07-23no document linked
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/wk37k stars

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.

Vibe-Trading

Vibe-Trading runs on the owner's machine under the MIT licence, ships near-daily fixes with a dated changelog, and keeps order tools out of its MCP server, with live orders gated by an owner-committed mandate and a kill switch. Three advisories, two critical, covered versions before 0.1.7, and the local CLI runs shell commands without asking.

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

Vibe-Trading

  1. Run 0.1.7 or later. Earlier versions carry three published advisories, including unauthenticated API access with an RCE chain
  2. Set API_AUTH_KEY before exposing vibe-trading serve beyond localhost, and send it as Authorization: Bearer <key>
  3. Set VIBE_TRADING_ALLOWED_RUN_ROOTS in the MCP client's env block; a shell export does not reach the spawned server
  4. Use vibe-trading run -p "..." --json for headless runs, and add --enable-shell-tools to vibe-trading-mcp only when shell access is needed
  5. Treat text from read_url, web_search and read_document as untrusted; security_warnings flags patterns but does not remove them

Questions

Which is better for AI agents, Paperclip or Vibe-Trading?

Vibe-Trading scores 62.2 (B) on agent readiness against Paperclip's 59 (C), and leads in 2 of 7 scored categories. Paperclip leads on schema & documentation and transparency & trust.

Are Paperclip and Vibe-Trading open source?

Yes. Paperclip is open source (MIT). Vibe-Trading is open source (MIT).

Other comparisons with Paperclip or Vibe-Trading

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.