Run Paperclip locally for agent orchestration, AI company setup, and OpenClaw, Codex, or Claude control-plane operations.
On first use, read setup.md for integration guidance.
User needs to install, operate, or evaluate Paperclip as the control plane for a team of AI agents. Use for local-first setup, agent-company design, adapter selection, OpenClaw integration, CLI operations, and API-based coordination.
Skill memory lives in ~/paperclip/. Paperclip application data usually lives in ~/.paperclip/instances/. If ~/paperclip/ does not exist, run setup.md. See memory-template.md for structure.
~/paperclip/
├── memory.md # Operator context, active instances, adapter preferences
├── companies.md # Company names, goals, and status snapshots
├── commands.md # Reused CLI/API snippets that worked
└── notes.md # Open questions, blockers, migration notes
| Topic | File |
|---|---|
| Setup process | setup.md |
| Memory template | memory-template.md |
| Local bootstrap | quickstart.md |
| Adapter selection | adapters.md |
| Daily operator commands | operations.md |
| OpenClaw integration | openclaw.md |
paperclipai package and local servercurl for direct API checks and automationnpx paperclipai onboard --yes for the first working instance.--data-dir when testing in a throwaway environment or when isolation matters.codex_local or claude_local when the agent should run on the same host as Paperclip.openclaw_gateway when OpenClaw lives outside the control plane and should be hired as an employee.localhost from inside OpenClaw Docker -> the container points to itself, not the Paperclip host.| Endpoint | Data Sent | Purpose |
|---|---|---|
http://localhost:3100/api or configured Paperclip API base | Company, agent, issue, approval, and run metadata | Control-plane reads and writes |
ws://127.0.0.1:18789 or configured OpenClaw gateway URL | Wake payloads, session routing, streamed agent events | OpenClaw adapter transport |
No other endpoints should be contacted unless the user explicitly configures remote deployments or model providers.
Data that leaves your machine:
Data that stays local:
~/.paperclip/instances/~/paperclip/This skill does NOT:
By using this skill, operational data is sent to the Paperclip deployment and agent adapters the user configures. Only install if you trust that deployment, its storage, and the model providers behind those agents.
Install with clawhub install <slug> if user confirms:
agent — General agent execution and delegation patternsagents — Multi-agent coordination and role designcompany — Company-level strategy and operating structureworkflow — Repeatable operational workflows and handoffsapi — Direct API usage, payload design, and HTTP troubleshootingclawhub star paperclipclawhub syncZIP package — ready to use