OpenBot vs paperclip
CopilotKit's self-hosted AI coworkers: each gets its own computer — a real browser with logins, files, granted tools — with every action decided before it runs and recorded after. Any AG-UI agent. — versus — Open-source control plane for running fleets of heterogeneous AI agents as a "company" — bring your own agent, assign goals, org charts, budgets, governance, and an audited ticket system.
Both run fleets of heterogeneous agents as a 'company' with bring-your-own agent. Paperclip is the control plane — org, roles, budgets; OpenBot gives each coworker a governed computer and a channel, with AG-UI as the contract.
| OpenBot | paperclip | |
|---|---|---|
| Stars | 4.3k | 80k |
| Forks | 531 | 15k |
| Language | TypeScript | TypeScript |
| License | MIT | MIT |
| Last activity | today | 2 days ago |
| Topics | agents, orchestration | agents, orchestration |
| Curated connections | 4 | 8 |
OpenBot — the curator's take
A template for running agents you'd trust with real access, on your own infrastructure: Docker Compose, your Postgres, your model credential, and coworkers defined in agents.yaml. Because a Bot is any endpoint speaking AG-UI, agents built on LangGraph, Mastra, CrewAI, Pydantic AI or Google ADK arrive the same way and the governance rides the protocol — watch a coworker on its own screen, take the wheel at a decision it shouldn't make alone, hand it back. NOT a product: nothing is published as a package, there is no hosted version, you clone it and replace the example tenant. Alpha, and single-user by default until you wire OAuth.
paperclip — the curator's take
Reach for Paperclip when you run many agents across providers 24/7 and need a boss layer — budgets that hard-stop, org charts, goal alignment, audit trail, mobile monitoring. Sweet spot: "20 Claude Code tabs, lost track of who does what." NOT the tool to build an agent (it orchestrates ones you already have), and overkill for a single agent or one linear pipeline. It's a control plane, not a framework.