PaperClip AI: The Open-Source Framework That Turns AI Agents Into a Full Company
From Single Agents to Autonomous Organisations
For the past year, most developers working with AI tooling have been thinking in terms of individual agents: one Claude Code session spinning up, doing a job, shutting down. Useful, but fundamentally limited. You can only parallelise so far before you're juggling 20 terminal windows with no shared context, no cost visibility, and no way to recover state after a restart.
That is the exact problem PaperClip was built to solve.
Launched on 4 March 2026 by the pseudonymous developer @dotta, PaperClip is an open-source multi-agent orchestration framework that organises AI agents into a functioning company structure. It is a Node.js server with a React UI that orchestrates a team of AI agents to run a business — with org charts, budgets, governance, goal alignment, and agent coordination — all managed from a single dashboard. Within three weeks of launch, it hit 30,000 GitHub stars, signalling something bigger than developer hype.
The origin story is telling. @dotta built PaperClip because he was using Claude Code to run his companies and would have 20 or 30 Claude Code windows open at once, with no way to track what any of them were working on. PaperClip is the infrastructure layer that was missing.
What PaperClip Actually Does
PaperClip does not replace your AI agents. It sits on top of them.
Paperclip is fundamentally different from frameworks like CrewAI or AutoGen: it does not build agents. It takes existing agents — Claude Code, OpenClaw, Codex, Python scripts, HTTP webhooks — and organises them into a functioning company.
The mental model is straightforward. You are the board of directors. You define a high-level company goal — something like "grow the newsletter subscriber base by automating content creation and improving open rates." A CEO agent then interprets that goal, proposes a hiring plan, and — with your approval — spins up specialised sub-agents: a researcher, a writer, a reviewer, an engineer. Each agent has a defined role, a system prompt, and a clear reporting line.
From that point, the company runs itself on a schedule.
The mechanism driving autonomous operation is the heartbeat. The CEO agent wakes up at a configurable interval, reviews the task pipeline, assigns work to idle agents, picks up completed tickets for review, and queues the next cycle. You can set the heartbeat to run every ten minutes during active development or every hour in steady-state operation. Skills — markdown instruction files — teach agents specific workflows. They can be applied company-wide or scoped to individual agents, and imported via GitHub URLs for automatic updates.
The Technical Architecture
PaperClip requires meaningful technical ability to set up and operate. You need comfort with command-line tools, Node.js (version 20+), pnpm package management, environment variables, and reading documentation. This is not a no-code experience.
Installation is a single terminal command. The server exposes a React dashboard accessible over the browser, which you can run locally on your own machine or deploy to a virtual private server for 24/7 autonomous operation. The VPS route is strongly recommended: running fully autonomous agents with filesystem access on a personal machine creates obvious security and availability risks. Docker deployment on a cloud provider gives you isolation, uptime, and a recoverable environment.
What makes PaperClip different from the growing list of agent frameworks is its "bring-your-own-bot" philosophy. It works with Claude Code, Codex, OpenCode, Cursor, and any model on OpenRouter. You configure each agent with an adapter that points to whichever provider you want — Claude for nuanced extraction tasks, a faster model for structured formatting, Codex for code generation. Different agents in the same company can use different providers simultaneously.
Cost tracking is built in. The platform supports per-agent monthly budgets that auto-pause spending at 100% utilisation. If you are running on API credits, you can set hard limits per agent so a runaway task does not drain your quota overnight. If you are running on a Claude Code Max or Codex subscription, you bypass per-token billing entirely, though you need to authenticate the subscription from within the Docker container via SSH.
The Issue-Based Workflow
PaperClip is not a chatbot interface. There is no conversational back-and-forth. Instead, the workflow revolves around issues — tasks you create and assign, much like a Jira or Linear ticket.
You create an issue with a description, a priority level, and an assignee. If you assign it to the CEO with a critical priority, it gets picked up immediately on the next heartbeat cycle. If you leave it unassigned, the CEO will pick it up autonomously and delegate it as appropriate.
The Kanban board tracks work across states: backlog, to do, in progress, in review, blocked, and done. Blocked tickets are particularly useful — when an agent cannot proceed because it lacks a credential, a connection, or a missing piece of context, it surfaces a blocked ticket explaining exactly what human intervention is needed. You resolve the blocker, flip the ticket back to in progress, and the agent picks up where it left off.
The inbox aggregates anything the CEO thinks you need to see: hiring requests from sub-agents, completed deliverables awaiting your sign-off, and alerts about stalled work. You are involved at the governance level — approving hires, unblocking issues, reviewing strategy — without manually orchestrating every task.
Agent Prompt Engineering: The Real Leverage Point
The difference between a PaperClip company that produces useful work and one that idles is almost entirely in the system prompts.
By default, agents can be reactive rather than proactive — waiting for tasks rather than seeking them out. The fix is explicit: write a CEO system prompt that defines a repeatable heartbeat protocol. Phase one, status check. Phase two, review completed work. Phase three, assign work to idle agents. Phase four, review metrics and adjust strategy. When the CEO has a structured workflow to follow on every cycle, it stops saying "nothing to do" and starts acting like an operator.
The same principle applies to every specialist agent. A newsletter researcher needs to know exactly what output format to produce, what sources to check, and what to hand off to the writer. A founding engineer needs explicit instructions about committing to feature branches, never pushing to main, and always raising a pull request. The more precisely you define the process in the prompt, the more reliably the agent executes it.
What Is Coming Next
PaperClip's roadmap includes Clipmart, a marketplace where users will be able to download pre-built company templates — content agencies, trading desks, development shops — all with org structures, agent configs, and skills baked in, importable into a PaperClip instance in one click.
The AI agent market is projected to grow from $7.84 billion in 2025 to $52.62 billion by 2030, at a 46.3% compound annual growth rate, with multi-agent systems representing the highest-growth segment at 48.5% CAGR. PaperClip is an early but serious attempt to build the coordination infrastructure that market growth requires.
There is no managed cloud version of PaperClip as of mid-2026. You are entirely responsible for your own infrastructure — provisioning servers, maintaining uptime, handling updates, and managing backups. For technical founders and developers comfortable with DevOps overhead, that is a reasonable trade-off for full control. For everyone else, it remains a barrier.
The technology is not fully mature. Agents still get stuck, still require human unblocking, and still benefit from hands-on prompt tuning. But the architecture is sound, the GitHub traction is real, and the problem it solves — coordinating multiple autonomous agents toward a shared business goal — is one that every developer working with AI at scale will eventually face.
PaperClip is worth running today. It will be essential tooling within the year.
PaperClip is available at github.com/paperclipai/paperclip under the MIT licence.











