Paperclip

Overview

Paperclip is an open-source orchestration platform that reframes AI agents as employees in a company. Instead of managing a pile of scripts and Claude Code tabs, you define an org chart with roles, reporting lines, budgets, and governance — then let agents work autonomously within that structure.^[1]

The project hit 53,000+ GitHub stars in its first 6 weeks (created March 2, 2026), and the momentum has held: as of June 11, 2026 it stands at 69,955 stars, 12,980 forks, and 105 contributors, with commits pushed the same day.^[2] MIT licensed and fully self-hosted via npx paperclipai onboard.^[3]

Notably, the project has softened its positioning. The original tagline — "open-source orchestration for zero-human companies" — has been replaced with "the app people use to manage AI agents for work."^[1] The architecture is unchanged; the pitch moved from replacing humans to managing agents alongside them.

The core insight, as one early user put it: "The framing here is what makes this interesting. Not 'here is an AI tool.' CEO hires a Coder. You approve it. The mental model is a company you are running, not a tool you are using. The shift from 'I am prompting an AI' to 'I am managing a team' changes how you think about what's possible."

Key Concepts

Org Chart as Architecture

Agents don't freelance — they have a boss, a title, and a job description. The CEO agent can delegate to a CTO, who delegates to engineers. Reporting lines define delegation flow.

Heartbeats

Agents wake on a schedule, check their work, and act. Delegation flows up and down the org chart automatically. Cross-team requests route to the best agent for the job.

Goal Alignment

Every task traces back to the company mission:

• Company Mission — "Make $2M ARR with the #1 AI note-taking app"
• Project Goal — "Ship collaboration features"
• Agent Goal — "Implement real-time sync"
• Task — "Write WebSocket handler for document updates"

Agents always know what to do and why through this context chain.

Cost Control

Monthly budgets per agent. When they hit the limit, they stop. Track costs per agent, per task, per project, per goal. No runaway token spending.

Ticket System

Every conversation is a ticket. Every instruction, response, tool call, and decision is recorded with full tracing. Append-only audit log — no edits, no deletions.

Governance

The human operates as the board of directors:

• Agents can't hire new agents without approval
• CEO can't execute unapproved strategy
• Pause, resume, override, reassign, or terminate any agent at any time
• "Autonomy is a privilege you grant, not a default"

Multi-Company

One deployment, many companies. Complete data isolation between businesses. Designed for running a portfolio of autonomous businesses from one control plane.

Agent Compatibility

Paperclip is agent-agnostic — "If it can receive a heartbeat, it's hired". The supported roster has grown since April 2026:^[1]

• OpenClaw — Personal AI agents
• Claude — Anthropic's Claude models
• Codex — OpenAI's coding agent
• Gemini — Google's models; the Gemini CLI now ships in the production Docker image^[4]
• Cursor — AI IDE
• Hermes — Agent framework adapter
• Pi and OpenCode — Additional agent runtimes
• Bash — Shell scripts and automation
• HTTP — Any API endpoint

External adapter plugins can hot-install over built-in adapter types, so newer agent implementations can replace the bundled ones without forking.^[4]

Community Templates

Pre-built company templates for common use cases:

Trajectory Since April 2026

Releases ship on a roughly biweekly cadence (v2026.529.0 on May 30, v2026.609.0 on June 9). Notable additions since April:^[4]

• Company Artifacts — files, media, and documents agents produce are indexed on a company-scoped page with upload and rich playback
• Plugin system with external adapters — plugins can override built-in agent adapters; agent-issued JWTs can call plugin tool endpoints
• Routines — scheduled routine ticks, suppressed while a project is paused
• Automated PR quality and security gates — commitperclip checks linked issues, test coverage, and lockfiles on incoming PRs, paired with prompt-injection-resistant "low-trust review containment" for reviewing untrusted content
• CLI/API parity — broader OpenAPI coverage so agents can mutate their own issues via the CLI

The sustainability question from April remains open in one direction and answered in another. Answered: the project did not stall — release velocity, contributor count, and star growth all continued. Open: there is still no disclosed company, team, or funding. The pseudonymous lead (@dotta, who gave an April interview as Paperclip's "CEO" without revealing further identity) authors the large majority of merged PRs in each release.^[5][4]

Competitive Positioning

Paperclip occupies a unique position in the agent orchestration landscape:

As one community member noted: "OpenClaw is an employee, Paperclip is the company."^[6]

Relationship to Tembo

Paperclip and Tembo solve different problems at different altitudes:

• Tembo orchestrates coding agents for engineering teams — integrating with GitHub, Linear, Jira, Sentry, and databases for developer workflows
• Paperclip orchestrates agents across entire business functions — engineering, marketing, sales, operations — using an org-chart metaphor

They're complementary rather than directly competitive. A Paperclip company could use Tembo as the orchestration layer for its CTO/engineering department while Paperclip handles the cross-functional coordination.

Strengths

• Sustained adoption, not just a spike — 69,955 stars as of June 2026, up 31% since April, with same-day commit activity^[2]
• Real contributor base — 105 contributors and a steady biweekly release cadence^[2][4]
• Open source (MIT) — Self-hosted, auditable, no vendor lock-in
• Agent-agnostic — Eight named agent adapters plus Bash and HTTP; plugins can override built-ins^[1]
• Multi-company — Run a portfolio of autonomous businesses from one install
• Cost control — Per-agent budgets with automatic pause at 100% utilization^[1]
• Full audit trail — Append-only ticket/trace system for accountability
• Great UX — Multiple users compare design quality to Linear

Cautions

• Still very young — Created March 2, 2026; roughly three months old. The trajectory is good but short
• Pseudonymous, unfunded, single-maintainer-heavy — No disclosed company, team, or funding as of June 2026; the lead developer gave an April interview only as "Paperclip's CEO" under a pseudonym, and release notes show one account (@cryppadotta) authoring most merged PRs. Bus factor is the project's biggest structural risk^[5][4]
• Issue backlog outpacing maintainers — 4,953 open issues against 105 lifetime contributors as of June 11, 2026^[2]
• Self-hosted only — Still no managed cloud option or paid tier; reviewers note real costs are servers plus model tokens, and there is no commercial entity to buy support from^[7]
• Hype-to-substance ratio — Community reception (including the r/openclaw thread) is enthusiastic about the framing, but star counts still overstate verified production usage^[6]
• Template quality — Pre-built templates are starting points, not production-ready businesses

Key Stats

Bottom Line

Paperclip answered the easy half of April's sustainability question: it was not a hype-cycle casualty. Stars grew from 53,487 to 69,955, releases ship biweekly, and the feature surface (artifacts, plugins, routines, PR security gates) is maturing fast. The hard half is unchanged — a pseudonymous lead, no disclosed funding, no commercial entity, and an issue backlog near 5,000.

Recommended for: technically capable operators and tinkerers who want the org-chart orchestration model, can self-host, and accept community-only support.

Not recommended for: enterprises needing a vendor relationship, SLAs, or accountability from an identifiable legal entity — none exists yet.

Outlook: the category leader by adoption, with the strongest momentum in the comparison. The decisive question for the next six months is whether a company or foundation forms around it; without one, governance and support remain a single pseudonymous developer's goodwill.

---

Research by Ry Walker Research · methodology