core vs paperclip
Self-hosted, always-on "personal AI OS": watches your apps, keeps a persistent memory graph, and acts autonomously within guardrails — a product, not a library for building agents. — 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 are the layer ABOVE agent frameworks rather than a framework themselves, and both spawn coding-agent sessions — but CORE is a personal, memory-driven, always-on assistant while paperclip manages fleets of agents as a team/company. Pick CORE for a personal AI OS, paperclip for multi-agent org governance.
| core | paperclip | |
|---|---|---|
| Stars | 1.9k | 74k |
| Forks | 181 | 14k |
| Language | TypeScript | TypeScript |
| License | NOASSERTION | MIT |
| Last activity | yesterday | yesterday |
| Topics | agents, memory | agents, orchestration |
| Curated connections | 6 | 7 |
core — the curator's take
Reach for CORE when you want an event-driven, self-hosted personal assistant that notices things on its own, remembers across sessions via a memory graph, and acts across your apps with per-action approval gates. NOT the pick if you want a framework to embed agents inside your own software (it's a product/OS, not a toolkit), nor if you need to run a multi-agent team/company with org charts and budgets — that's paperclip's lane.
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.