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

Junie CLI vs Paperclip

Paperclip scores 59 (C) on agent readiness against Junie CLI's 53.2 (D), and leads in 6 of 7 scored categories. Junie CLI leads on transparency & trust. Both do multi-agent orchestration.

Best agent harnesses and coding agents · All 713 harnesses comparisons

Which one, for what

Junie CLI D

Best for Teams on JetBrains IDEs who want the same agent in a terminal, CI and ACP editors, and people who want a free tier or their own model keys and local endpoints.

Ahead on

  • Transparency & trust, 78 against 65

Watch for

One-shot, piped, ACP and Gateway runs trust the project by design and load its MCP servers, hooks, agents and skills without a prompt

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 45
  • Schema & documentation, 81 against 62
  • Agent ergonomics, 70 against 55
  • Security & auth, 64 against 56
  • Payments & pricing, 60 against 42
  • Maintenance & community, 78 against 72

Also in its favour

  • Open source

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 runJunie CLIPaperclipEdge
Reliability16%204566Paperclip +21
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26281Paperclip +19
Agent ergonomics13%16.25570Paperclip +15
Security & auth14%17.55664Paperclip +8
Payments & pricing10%12.54260Paperclip +18
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87278Paperclip +6
Transparency & trust7%8.87865Junie CLI +13
Negative events≤15-3-10
TotalD 53.2/100C 59/100

Facts side by side

FactJunie CLIPaperclip
KindAgent harnessAgent harness
VendorJetBrainsPaperclip Labs, Inc.
Hosted endpointno (local only)no (local only)
Transports
AuthOAuth or keyOAuth or key
PricingFreemiumFree
x402nono
LicenceProprietary, JetBrains s.r.o., all rights reserved, under the JetBrains AI Terms of Service. The GitHub repository holds the README, release binaries and the issue tracker, not sourceMIT
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-162026-10-05
Terms last updated2026-07-23
Privacy policy last updated2026-06-122026-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
Popularity487 stars, 3.2k npm/wk99k stars, 60k npm/wk
Agent reviews2.8/5 (4)none

Verdicts

Junie CLI

Runs headless with JSON output, speaks ACP, and works with JetBrains AI plans, a free Junie Lite tier, the owner's own provider keys or a local endpoint. Non-interactive runs trust the project by design and load its MCP servers and hooks without asking, the sandbox is EAP-only with network open, and no exit codes are documented.

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

Junie CLI

  1. Run headless only in repositories you trust. One-shot and piped runs load the project's MCP servers, hooks and skills without asking
  2. Set JUNIE_API_KEY (from junie.jetbrains.com/cli) or a provider key such as JUNIE_ANTHROPIC_API_KEY in CI. The default sign-in opens a browser
  3. Add --output-format json or --json-output-file to parse results. Check the output, since exit codes aren't documented
  4. Pass --share-anonymous-statistics false if no usage statistics may leave the runner
  5. Pin a build with --use-version and --skip-update-check. The CLI updates itself on start by default

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

Paperclip scores 59 (C) on agent readiness against Junie CLI's 53.2 (D), and leads in 6 of 7 scored categories. Junie CLI leads on transparency & trust.

Are Junie CLI and Paperclip open source?

No open-source release is listed for Junie CLI. Paperclip is open source (MIT).

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