Paperclip AI Review: I Tried to Build a Zero-Human Company in a Weekend
Paperclip AI is an open-source app for running a team of AI agents as a company: org chart, goals, budgets and approval gates. What it does, how heartbeats and governance work, and why a "zero-human" company still needs a human.
Paperclip AI is an open-source, self-hosted app that runs a team of AI agents (Claude Code, Codex, Cursor, OpenClaw and others) as if they were a company, with an org chart, goals, budgets and approval gates managed from one dashboard. It is a Node.js server and React UI, MIT-licensed, and published by Paperclip Labs on GitHub since March 2026.

Its README sums up the pitch in one line: "If OpenClaw is an employee, Paperclip is the company." You define a goal, hire a team of agents into roles such as CEO, CTO, engineers and marketers, review the strategy, set budgets, and let the team run while you monitor it from the dashboard.
Is Paperclip AI worth trying? Yes, for an hour, if you already juggle several coding agents. It is free and self-hosted, and the npx paperclipai test-drive command starts an isolated instance with a CEO agent ready to go. It will not run a company on its own: its workflow still has a human reviewing the strategy, setting budgets and approving the run.
What Is Paperclip AI and How Does It Work?
Paperclip is developed in the open at github.com/paperclipai/paperclip. The repository was created on March 2, 2026, is MIT-licensed, and had more than 105,000 stars by October 2026. No Paperclip account is required: you run it on your laptop, in Docker, or on a server.

Here's how it works in practice. You install it with npx paperclipai@latest onboard --yes (Node.js 24.11 or newer), create a company and give it a goal. Agents are "hired" into an org chart with roles, titles, reporting lines and budgets, and almost any runtime can be an employee. The README's rule is "If it can receive a heartbeat, it's hired."
Agents don't run continuously. They wake on a heartbeat (for assigned work, a follow-up message, or a configured schedule), check out a task, do the work and report back, with delegation flowing up and down the org chart. Each task carries its parent goal, so an agent sees why it is doing the work, not just a ticket title.
If you've been following multi-agent AI systems moving from demos to production, the architecture will feel familiar. Paperclip is a control plane for that idea: it doesn't build agents, it manages the organization they work in.
What Paperclip Manages: Budgets, Governance and Routines
Budgets. Budgets can be set per company, agent and project. Paperclip tracks token spend by agent, project, provider and model, sends threshold alerts, and pauses work at hard limits. The README notes that enforcement uses recorded spend, so usage reporting and in-flight work can delay a stop.

Governance. Board approval workflows, review and approval stages on tasks, approval of new hires, and the ability to pause, reassign or terminate an agent are built in. Config changes are revisioned and can be rolled back.
Routines. Recurring work runs from a cron schedule, a webhook or an API call. Each run creates a tracked task assigned to an agent, so jobs like reports or support triage don't need a manual kick-off.
Connections and audit. Agents can use services such as GitHub, Notion and Railway or your own MCP server, and each gateway action can be set to Allowed, Ask first, or Off. Mutating actions, approvals and cost events are recorded as durable activity, so operators can audit what happened and why.
Metics Media has a video walkthrough, "Paperclip AI Tutorial: How to Build a Zero-Human Company":
Where Paperclip AI Still Needs a Human
Paperclip's own README is explicit that "zero-human" doesn't mean unsupervised. It is for people who want agents running autonomously 24/7 "but still want to audit work and chime in when needed," and it sums up its task manager as "Declare intent. Agents work. You verify the output."
That matters because the hard part of building a company isn't generating ideas or drafting documents. It's judgment: knowing which of ten possible directions is the right one, and catching the subtle error that looks correct to everyone except someone with domain expertise.
Paperclip doesn't supply that judgment. Agents bring their own prompts, models and runtimes, so output quality depends on what you hire; Paperclip provides the review gates, budgets and audit trail around them.
Context is the other hard part. Paperclip keeps tasks, comments and documents in one place, and supporting adapters resume saved sessions across runs. For the agent side of that problem, see AI Agent Memory State Management Guide [2026].
Paperclip is not an agent framework like CrewAI or Microsoft's AutoGen. In the README's words: "We don't tell you how to build agents. We tell you how to run a company made of them." Custom processes and HTTP endpoints can be hired as agents too, so the two layers can sit side by side.
If you've been exploring the agent ecosystem, my comparison of OpenClaw vs CrewAI digs deeper into what separates a toy demo from a production-grade agent framework. The gap is enormous.
Can Paperclip AI Actually Build a Working Business?
Short answer: not on its own. Paperclip is pitched at autonomous AI organizations ("the agents take care of the rest"), but its own workflow still puts a human at the "Approve and run" step: review strategy, set budgets, hit go, monitor.
That distinction matters. What Paperclip ships is management infrastructure: tickets, org charts, budgets, approvals and logs. The business outcome still depends on the agents you hire and on the person reviewing their work.
The danger isn't that AI agents can't do work. It's that they can't tell you when the work they've done is wrong.
This is the core tension in every autonomous agent system right now: getting from mostly correct to reliably correct is where the real engineering lives. Paperclip's answer is to make the review step explicit rather than skip it.
The Bigger Question: Are We Ready for Zero-Human Operations?
Paperclip is a provocative project and an unusually popular one: the GitHub repository, created on March 2, 2026, had more than 105,000 stars by October 2026. It also shows why "zero-human" companies aren't viable without oversight, since much of its feature list is about keeping humans in control.
The risks any autonomous agent setup has to manage, and the Paperclip feature aimed at each:
- Unverified output. Agents can state things that aren't true. Paperclip's answer is review and approval stages before a task counts as done.
- Unreviewed code. Coding agents can work in isolated git worktrees, and their work can be verified from diffs, screenshots and tests.
- Actions on your behalf. Connected services sit behind a gateway where each action can be Allowed, Ask first, or Off.
- Runaway spend. Budgets with warning thresholds and hard stops pause work at configured limits, and an agent can be paused or terminated.
I've written before about how AI coding agents won't replace engineers but will change how we think about code. The same principle applies here, amplified. AI business agents won't replace founders. But they will change how we think about the early stages of company building. If we're honest about their limitations.
That dynamic plays out at scale in ways that are just as counterintuitive — AI Coding Assistant Team Adoption: What Breaks After Everyone Gets a License [2026] unpacks exactly how teams experience a confidence boost while actual delivery slows down, which is a useful lens for thinking about what happens when autonomous agents touch your production pipeline.
If the PR volume spike is what worries you most, I wrote AI Coding Team Workflow Policy Guide [2026]: Stop the PR Flood as a concrete policy template for labels, ownership, review SLAs, and enforcement when AI tools start generating more changes than humans can realistically review.
What Paperclip AI Gets Right
Three design choices stand out:
- Bring your own agent. Any runtime that can receive a heartbeat can join the org chart, including Claude Code, Codex, Cursor, Gemini CLI, OpenCode and OpenClaw, so you aren't locked to one model provider.
- Work is visible and auditable. Tasks are tickets, conversations are threaded, sessions persist across reboots, and every mutating action, approval and cost event is logged.
- Cost control is first-class. Company, agent and project budgets with alerts and automatic pauses target the problem the README calls out: runaway loops that "waste hundreds of dollars of tokens and max your quota before you even know what happened."
The Verdict
Paperclip AI is not going to build your company for you. Full stop. But it might change how you think about what's possible.
If you're a developer already juggling several coding agents, it's worth an hour. The npx paperclipai test-drive command starts an isolated instance that already has a CEO agent, so you can see how far tickets, budgets and approvals get you before running it for real.
Photo by Vitaly Gariev on Unsplash.
Kunal Ganglani (2026, April 19). Paperclip AI Review: I Tried to Build a Zero-Human Company in a Weekend. Kunal Ganglani. Retrieved November 22, 2026, from https://www.kunalganglani.com/blog/paperclip-ai-review-zero-human-company
Frequently Asked Questions
Is Paperclip AI free?
Yes. Paperclip is open source under the MIT license and self-hosted, and it needs no Paperclip account. You pay for the models and agent runtimes you connect. A hosted Paperclip Cloud has a waitlist.
How does Paperclip AI work?
You install Paperclip, create a company with a goal, and hire AI agents (Claude Code, Codex, Cursor, OpenClaw or any runtime that can receive a heartbeat) into an org chart. Agents wake on heartbeats to pick up assigned tasks, delegate up and down the chart, and report back, while you set budgets, approve work and monitor everything from a dashboard.
Who created Paperclip AI?
Paperclip is published by Paperclip Labs, Inc. (named in the README's MIT license line), and is developed in the open at github.com/paperclipai/paperclip. The repository was created in March 2026.
Is Paperclip AI good?
It is good at the management layer: org charts, task tickets, heartbeats, budgets, approval gates and an audit log for a team of AI agents. It does not make the agents themselves more accurate; output quality depends on the models and runtimes you hire, which is why its review and approval features matter.
What is a zero-human company in Paperclip AI?
It is a business run by coordinated AI agents rather than human employees. Paperclip is built for that kind of autonomous AI organization, but its README still expects a human to review strategy, set budgets, approve work and "chime in when needed."



