Cline vs Paperclip

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, 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.

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. Untick 'Allow error and usage reporting', or turn off VS Code telemetry, before the first task
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

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