Tech Radar POC · 2026-04-19 · Live Run
Paperclip Agentic Orchestration POC
Org charts, heartbeats, and budget controls for monday.com AI agents
Use Case
The monday.com Fit
Hypothesis
"When you have 10+ AI agents running in parallel — coding, researching, reviewing — Paperclip is the management layer that keeps them coordinated, budgeted, and auditable."
- ✅
20 Claude Code tabs open? Paperclip turns that into a ticket queue with assignments, status, and context threading.
- ✅
OpenClaw as a Paperclip employee — explicitly supported. OpenClaw is listed as a first-class adapter. "OpenClaw is an employee; Paperclip is the company."
- ✅
Directly relevant for AI Innovation team — org-wide agent config, reproducible setups, agent governance.
- ✅
On-prem / self-hosted — single Node.js process, no Paperclip account required, full data isolation.
Architecture — Live POC
How the Loop Actually Works
Paperclip → Fires scheduled heartbeat on Radar agent (cron or on_demand)
→ Process adapter runs openclaw-heartbeat.sh with env: PAPERCLIP_AGENT_ID, PAPERCLIP_API_URL
→ Script calls openclaw agent --session-id main --message "[Paperclip Heartbeat] ..."
→ OpenClaw wakes the main session, processes the wake event
→ Agent replies: HEARTBEAT_OK
→ Script exits 0 → Paperclip marks run succeeded
Live confirmed
Run ID 0c0569b2 — Status: succeeded · ExitCode: 0 · stdout: "HEARTBEAT_OK"
Results — Engineering Notes
Blockers Hit → All Resolved
- Embedded Postgres rejects root user→ Docker postgres:16-alpine workaround
missing scope: operator.write on heartbeat WS→ Root-caused: disableDeviceAuth:true strips all scopes. Fixed with stable Ed25519 keypair + device approvalinvalid agent params: unexpected property 'paperclip'→ Schema mismatch: paperclipai 2026.416.0 sends fields OpenClaw 2026.3.28 rejects. Updated OpenClaw to 2026.4.15- openclaw_gateway adapter still fails after update→ Switched to process adapter + CLI bridge. Cleaner, no WS schema dependency
- OpenClaw
agent command needs session target→ --session-id main routes to the main active session
Known gap
The openclaw_gateway adapter needs openclaw to accept a paperclip field in agent params. Filed as a watch item — likely a minor schema update in a future OpenClaw release.
Evaluation
Paperclip vs. Current Alternatives
| Capability | Paperclip | Asana/Linear + OpenClaw | Raw scripts |
|---|
| Agent org chart + hierarchy | ✅ Native | ❌ Manual | ❌ |
| Per-agent monthly budget | ✅ Hard stop | ❌ | ❌ |
| Heartbeat scheduling | ✅ Built-in | ⚠️ Custom crons | ⚠️ DIY |
| Goal ancestry on tasks | ✅ Native | ⚠️ Manual | ❌ |
| Immutable audit log | ✅ Per run | ⚠️ Partial | ❌ |
| OpenClaw integration | ✅ First-class | ⚠️ Webhooks | ⚠️ Manual |
| Self-hosted, no account needed | ✅ | ❌ SaaS | ✅ |
| Setup effort | ⚠️ Medium (Docker + onboard) | ⚠️ Medium | ✅ Low |
Verdict
🟢
Ship it. Integrate.
End-to-end heartbeat loop confirmed live. The "org chart for AI agents" framing is unique and fills a real gap. Lowest-effort integration of any agent orchestration tool evaluated this quarter.
What works
Install in 1 command · Self-hosted · OpenClaw native · Heartbeat loop confirmed · Budget controls · Org chart + ticketing · Audit log
Watch items
openclaw_gateway adapter schema gap (use process adapter for now) · Embedded PG needs non-root or Docker · LLM provider must be configured separately
Recommendation
Three Concrete Next Steps
01
Internal Demo
Show the Paperclip UI to the AI Innovation team. Spin up a live instance with the monday.com use case: CEO agent decomposes a product goal, engineers (Claude Code) implement, Radar (OpenClaw) researches. 30-min live demo, high impact.
→ Effort: Low (instance already running)
02
Wire Bedrock LLM
The live POC used a process adapter bridge (no LLM). For real autonomous agent work, configure Paperclip's LLM provider (Bedrock/Anthropic) so the CEO agent can decompose goals and delegate tasks without manual intervention.
→ Effort: Low (paperclipai configure --section llm)
03
Submit openclaw_gateway Fix
The schema mismatch (paperclip field in agent params) between paperclipai 2026.416.0 and openclaw protocol is a 1-line schema fix. Worth filing upstream or patching locally to enable native WS adapter instead of the CLI bridge.
→ Effort: Low — open issue or PR to openclaw repo
Next Steps
What Happens Now
1
Repo is live — github.com/monday-ai-club/paperclip-monday-poc · setup_and_run.sh reproduces the full POC in one command
2
Internal demo — book 30 min with AI Innovation team, spin up the live instance, show the heartbeat loop and org chart UI
3
Configure LLM provider — npx paperclipai configure --section llm to enable CEO autonomous goal decomposition
4
Explore Clipmart — coming soon: one-click import of full company templates (pre-built org structures + agent configs)
5
Watch for native openclaw adapter — once the paperclip field schema lands in openclaw, swap process bridge for WS adapter
Deck + code
github.com/monday-ai-club/paperclip-monday-poc · Rendered deck: raw.githack.com/monday-ai-club/paperclip-monday-poc/main/deck/index.html