Project review
Orchestration for the zero-human company.
A serious control plane for agent teams: unusually strong on budgets, governance, and traceability, with operational reliability still awaiting an independent ClawLab pass.
By ClawBlog Reviews Desk · Drafted with ClawBlog's research pipeline; edited and accountable to the named reviewer.
84
/100
ClawScore
Strong
82
/100
Users' Score
example avg 8.2/10
Review consensus
ClawBlog critics
A serious control plane for agent teams: unusually strong on budgets, governance, and traceability, with operational reliability still awaiting an independent ClawLab pass.
84
/100
ClawScore
Strong
Review by ClawBlog Reviews Desk
Score profile
Readers
Approved reader ratings unlock at 5 ratings and stay moderated before publication.
82
/100
Users' Score
example avg 8.2/10 from 5
Paperclip: I kept this in the loop for a month of normal feature work. The strongest part was how quickly it recovered from messy repo state without making the review process feel brittle.
Paperclip: The setup path was smoother than expected and the defaults were sensible. I still had to tighten a few permissions for our workflow, but the day-to-day experience held up.
Example member reviews
Reader ratings for Paperclip, sorted newest first by default.
Featured
Mara Chen
9/10 · 18 helpful
Paperclip: I kept this in the loop for a month of normal feature work. The strongest part was how quickly it recovered from messy repo state without making the review process feel brittle.
Newest
Samira Okafor
8/10 · 8 helpful
Paperclip: The review queue and audit trail mattered more than raw speed for us. It was easy to understand what happened, what changed, and when a human needed to step in.
Jun 14, 20268 review karma
Paperclip: The review queue and audit trail mattered more than raw speed for us. It was easy to understand what happened, what changed, and when a human needed to step in.
8
/10
8
Helpful
Strong
Signal
Example reviews preview the voting surface, but they are not persisted and cannot receive votes.
Jun 13, 20269 review karma
Paperclip: I liked the basic shape, especially once I stopped treating it like a magic button and gave it bounded jobs. The rough edges were mostly around longer-running context.
7
/10
9
Helpful
Mixed
Signal
Example reviews preview the voting surface, but they are not persisted and cannot receive votes.
Jun 12, 202612 review karma
Paperclip: For repeatable agent tasks, the value showed up in the small things: clearer status, fewer surprise handoffs, and a useful paper trail when the output needed review.
9
/10
12
Helpful
Rave
Signal
Example reviews preview the voting surface, but they are not persisted and cannot receive votes.
Jun 11, 202614 review karma
Paperclip: The setup path was smoother than expected and the defaults were sensible. I still had to tighten a few permissions for our workflow, but the day-to-day experience held up.
8
/10
14
Helpful
Strong
Signal
Example reviews preview the voting surface, but they are not persisted and cannot receive votes.
Jun 10, 202618 review karma
Paperclip: I kept this in the loop for a month of normal feature work. The strongest part was how quickly it recovered from messy repo state without making the review process feel brittle.
9
/10
18
Helpful
Rave
Signal
Example reviews preview the voting surface, but they are not persisted and cannot receive votes.
The Criteria section is the detailed rubric behind the official ClawScore: each row carries its weight, rationale, and receipts.
Capability
Weight 1.6
The control plane spans goals, projects, atomic task checkout, heartbeats, persistent sessions, adapters, routines, workspaces, plugins, and multi-company operation.
Reliability
Weight 1.3
DB-backed queues, execution locks, recovery paths, and frequent releases are promising, but ClawBlog has not yet independently stress-tested failure recovery or long-running agent fleets.
Setup & DX
Weight 1.1
The one-command onboarding path, embedded local Postgres, documented manual setup, and production Postgres path make first use unusually direct for an orchestration control plane.
Safety & Control
Weight 1.4
Budget hard stops, approval policies, pause and terminate controls, scoped secrets, audit events, and operator overrides are first-class rather than bolted on.
Cost Efficiency
Weight 1
MIT licensing, self-hosting, bring-your-own agents, per-agent spend limits, and cost attribution give operators both a low entry price and meaningful spend control.
Docs & Support
Weight 1
The maintained guide and API reference cover setup, agents, governance, budgets, adapters, and day-to-day operations, backed by an active public repository and community.
Momentum
Weight 1.2
A large public contributor/user signal and a rapid signed-release cadence through July 2026 show exceptional current development momentum.
Paperclip has moved well beyond the thin orchestration concept captured in the original draft. It is now a substantial open-source control plane for teams of AI agents: a Node.js server and React interface built around company goals, projects, issues, agent hierarchies, scheduled heartbeats, persistent sessions, adapters, budgets, approvals, and an operator-visible activity trail.
The strongest part of the product is control. Task checkout and budget enforcement are designed as atomic operations; per-agent and company budgets can warn and hard-stop work; agents can be paused, reassigned, or terminated; approval policies can gate execution; and runs retain logs, costs, session state, and audit events. That is a much more credible answer to multi-agent risk than a diagram of agents talking to one another.
The setup and documentation story is also materially better than the earlier review recorded. A local installation can start through a single onboarding command with embedded Postgres, while production deployments can use an external Postgres database. The project documents its architecture and operating model, supports multiple agent runtimes and providers through adapters, publishes frequent signed releases, and is MIT-licensed.
Paperclip is also clear about where its responsibility ends. It does not try to replace the coding agents or model providers that perform the work; it supplies the organizational layer around them. Operators define company goals and reporting lines, connect their preferred agents, assign scoped work through projects and issues, and inspect the resulting run history in one place. That separation makes the system easier to evaluate than an all-in-one autonomy claim, and it leaves teams room to change execution providers without rebuilding their governance model.
The remaining reservation is empirical reliability. First-party documentation and release history establish feature depth and visible engineering activity, but they are not a substitute for ClawBlog exercising recovery, concurrency, budget enforcement, secret handling, and long-running multi-agent work under failure. Paperclip therefore earns a strong recommendation and a high score, while Reliability remains deliberately below the rest of the rubric until ClawLab supplies independent receipts.
Audience rating
Share one clear score and a short note. Approved reviews feed the Users' Score after moderation.
Checking session...
