# Paperclip vs T3 Code (slim)

> Paperclip and T3 Code score within a point of each other for multi-agent orchestration, 52.6 and 51.9 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/paperclip-vs-t3-code.md (~5,650 tokens) · this version ~2,230 tokens · JSON https://www.anchorterminal.com/compare/paperclip-vs-t3-code.json · canonical https://www.anchorterminal.com/compare/paperclip-vs-t3-code
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Paperclip and T3 Code score within a point of each other on agent readiness, 52.6 (D) and 51.9 (D). Both do multi-agent orchestration.

- Paperclip: D 52.6, rank #976 of 1486 · https://www.anchorterminal.com/tools/paperclip.min.md
- T3 Code: D 51.9, rank #1002 of 1486 · https://www.anchorterminal.com/tools/t3-code.min.md
- Paperclip, good for Someone running several coding or operations agents who wants one place for tasks, budgets, approvals and history across harnesses. Ahead on Reliability, 59 against 43; Schema & documentation, 81 against 55; Agent ergonomics, 70 against 60; Security & auth, 64 against 35; Transparency & trust, 66 against 51. Also Free to start without a card.
- T3 Code, good for Developers who want one app, including on their phone, to drive several coding agents they already pay for. Also No key needed to call it; No incidents deducted, where Paperclip loses 15 points for them.

| Category | Paperclip | T3 Code |
| --- | --- | --- |
| Reliability (16%) | 59 | 43 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 81 | 55 |
| Agent ergonomics (13%) | 70 | 60 |
| Security & auth (14%) | 64 | 35 |
| Payments & pricing (10%) | 60 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 78 | 75 |
| Transparency & trust (7%) | 66 | 51 |

| Fact (where they differ) | Paperclip | T3 Code |
| --- | --- | --- |
| Vendor | Paperclip Labs, Inc. | T3 Tools Inc. |
| Auth | OAuth or key | None |
| llms.txt | yes | no |
| Last release | 2026-10-23 | 2026-11-06 |
| Terms last updated | 2026-07-23 | no document linked |
| Privacy policy last updated | 2026-07-23 | no document linked |
| Customer content may train models | yes, with an opt-out | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | 99k stars, 60k npm/wk | none |

Why the edge:
- Security & auth, Paperclip +29: 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).); T3 Code 35 (Harness reading. Product usage events go by default to ingest.t3.codes and PostHog, with hashed identifiers for your T3 Connect, OpenAI and Claude accounts, and relay traces to Axiom, which can include machine names and error text. Off with T3CODE_TELEMETRY_ENABLED=false or a managed policy. Disclosed in docs/user/telemetry.md, not the README (10 of 30). Permission modes and managed policies (12 of 20). No prompt-injection guidance (5). No audit log (5). No security policy file found (3). 10 + 12 + 5 + 5 + 3 = 35.)
- Schema & documentation, Paperclip +26: Paperclip 81 (The running server publishes OpenAPI at `/api/openapi.json` and validates requests with Zod, and the MCP server's tools take Zod schemas. No copy of the spec is published on the docs site, and paperclip.ing/openapi.json describes only the website (22). llms.txt at paperclip.ing, and docs pages answer as Markdown at `.md` (10). An API reference page per resource and task guides, but the MCP tool descriptions are one line each, such as List agents in a company (13). Typed inputs throughout, apart from the `paperclipApiRequest` tool, which takes any path under `/api` and a JSON body (12). cURL, JavaScript and Python examples and a status-code table, with one `{error}` shape and an occasional `details` field (12). A changelog page for every stable release and release notes in the repository, but the API path carries no version (12).); T3 Code 55 (Harness reading. User docs in the repository (managed policy, handoffs, providers, telemetry), AGENTS.md for contributors, a server other clients connect to (55).)
- Reliability, Paperclip +16: 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.); T3 Code 43 (Local software. An install script and desktop and mobile apps from the vendor (20). ci.yml and windows-tests.yml run on the repository; pass state not read (15). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). Stable tags v0.1.5 to v0.1.7 with many nightlies, no changelog file (8). Version 0.1.7 (0). 20 + 15 + 0 + 8 + 0 = 43.)
- Transparency & trust, Paperclip +15: Paperclip 66 (MIT (30). The privacy policy of 23 July 2026 separates self-hosted use from the hosted services and names Paperclip Labs, Inc., but keeps data as long as reasonably necessary, lists no subprocessors, and the 90-day telemetry retention appears only in source. The terms grant a broad licence over content sent to the services and allow model training on opt-in detailed telemetry (16). Release notes carry dated Breaking Changes sections and upgrade guides, with no written deprecation policy or notice period (10). The README discloses telemetry, what it excludes and four opt-outs, and the event contract is public in the repository, but it is on by default (17).); T3 Code 51 (MIT (30). docs/user/telemetry.md lists what is sent and what isn't, but includes hashed third-party account identifiers and the README doesn't mention it (15 of 30). No deprecation policy (5). Disclosed with an opt-out, on by default (12 of 20). 30 + 15 + 5 + 12 = 62.)
- Agent ergonomics, Paperclip +10: Paperclip 70 (Harness reading of the framework line, scored on what an agent or pipeline driving it has to supply. The MCP server lists 44 tools with no toolsets or read-only subset found, offset by compact reads such as `paperclipInboxLite` and the heartbeat context (12). Budgets by company, agent and project with an automatic pause at 100 per cent, though the README says enforcement uses recorded spend and can lag work in flight (16). `onboard --yes`, CLI commands with `--json`, the REST API and routines started by cron, webhook or API (16). Atomic task checkout with a documented 409, `Idempotency-Key` on routine triggers, saved sessions and bounded recovery (17). One command starts a server with embedded PostgreSQL, but it needs Node.js 24.11 and each harness CLI installed and signed in on the host, and we found no client SDK beyond the TypeScript plugin SDK (9).); T3 Code 60 (Harness reading. Remote control from phone or browser, portable handoffs between providers and managed policies for teams (60).)