Paperclip

Ever wondered how to coordinate multiple AI agents like Claude Code, OpenClaw, and Codex without losing control? PaperClipAI is an open-source orchestration platform that solves exactly this problem. Here is the architecture diagram of the system. The core components include:

This post looks at Paperclip as an engineering system rather than as a product pitch. The useful question is how its parts exchange work, where state lives, and what happens when one part fails.

System overview

The project is organized around a small number of boundaries. Each boundary has a different job, and the interfaces between them are more important than the names of the individual components.

Main components

• A React dashboard for monitoring agents and tasks This boundary matters because it keeps one concern separate from the rest of the system.
• An Express.js API backend for orchestration This boundary matters because it keeps one concern separate from the rest of the system.
• A PostgreSQL database with company-scoped data isolation This boundary matters because it keeps one concern separate from the rest of the system.
• Adapters for multiple AI agent runtimes (Claude, Codex, OpenClaw, etc.) This boundary matters because it keeps one concern separate from the rest of the system.
• A heartbeat scheduler that wakes agents on schedule This boundary matters because it keeps one concern separate from the rest of the system.

Design questions

A system like this still needs clear answers before it is used in production:

• Where is durable state stored, and how does the system recover after a process or machine restarts?
• Which calls can be retried safely, and which operations need idempotency keys or a workflow record?
• What is the trust boundary between user input, generated code, external services, and local credentials?
• How are failures exposed to an operator instead of being hidden inside a queue, agent loop, or background worker?

Those questions are where the architecture becomes practical. A diagram can show the happy path; an implementation also needs the timeout path, the retry path, and the partial-failure path.

When it is useful

Ever wondered how to coordinate multiple AI agents like Claude Code, OpenClaw, and Codex without losing control? Paperclip is most useful when the team needs this workflow to be repeatable and inspectable, not when a one-off script would be easier to understand.

Source

The project is open source on GitHub. The original summary was shared on LinkedIn; this page expands it into an engineering note for the Ming Dao School library.