Paperclip Gateway Adapter

Paperclip AI adapter for OpenClaw Gateway protocol. Bridge between Paperclip and OpenClaw.

The Paperclip Gateway Adapter bridges OpenClaw with Paperclip — an ambitious open-source platform for orchestrating 'zero-human companies' where teams of AI agents run entire business operations autonomously. If OpenClaw is an individual employee, Paperclip is the company that hires and manages multiple OpenClaw instances as workers in an organizational hierarchy with budgets, goals, and governance. The adapter implements strict SSE (Server-Sent Events) streaming between Paperclip's orchestration layer and the OpenClaw Gateway protocol, supporting device-key pairing for secure authentication. When Paperclip needs an agent to perform a task, it routes the request through this adapter to an OpenClaw gateway, which handles the actual AI interaction, tool execution, and response streaming. The adapter manages the protocol translation — converting Paperclip's task-oriented commands into OpenClaw's session-based messaging format and streaming results back. With over 18,000 weekly downloads and a date-based versioning scheme (2026.318.0), the adapter is actively maintained as part of the Paperclip monorepo. Paperclip itself has gained significant traction — 14,000+ GitHub stars within its first week — by positioning as the missing management layer for AI agent fleets. The platform provides org charts, role-based hierarchies, budget enforcement, heartbeat-based scheduling, and immutable audit logging across multiple OpenClaw instances. This adapter is essential for anyone using Paperclip to orchestrate OpenClaw agents. It's not a standalone tool — you need both a running Paperclip server and one or more OpenClaw gateways. Best suited for power users running multiple AI agents who need coordination, budget tracking, and organizational structure. Not recommended for single-agent personal setups where OpenClaw alone is sufficient.

Tags: integration, adapter, tool

Use Cases

Orchestrating multiple OpenClaw agents as a team with defined roles (CEO, CTO, researcher, marketer)
Budget-controlled AI operations with per-agent monthly spend limits
Autonomous business operations running 24/7 with human oversight via dashboard
Multi-agent coding workflows where Paperclip coordinates and OpenClaw executes
Cost monitoring and audit trails across a fleet of AI agents

Tips

Start with a single OpenClaw gateway before scaling to multiple agents in Paperclip
Use Paperclip's budget enforcement to prevent runaway costs across your agent fleet
Check the Paperclip releases page for adapter-specific changelogs — they're bundled with main releases
For development, run both Paperclip and OpenClaw locally before deploying to separate servers
Use Paperclip's audit log to trace which OpenClaw agent performed which actions
Set up heartbeat schedules in Paperclip for recurring agent tasks rather than OpenClaw's built-in cron
Join the Paperclip Discord for community support — it's more active than GitHub issues for troubleshooting

Known Issues & Gotchas

The adapter is part of the Paperclip monorepo — you install it through Paperclip, not directly into OpenClaw
Earlier versions used a 'legacy adapter' pattern that has been replaced by the gateway-only flow
Device-key pairing must be completed before the adapter can communicate with OpenClaw
Budget enforcement is a Paperclip feature — the adapter itself doesn't track costs
If Paperclip and OpenClaw are on different machines, ensure WebSocket ports are accessible
Model selection happens in Paperclip's agent config, not in OpenClaw — this can cause confusion
The adapter streams responses via SSE — ensure your reverse proxy supports long-lived connections

Alternatives

OpenClaw built-in multi-agent (sub-agents)
CrewAI
AutoGen

Community Feedback

Have been using Paperclip for the past few days and I'm really impressed. It still has a long way to go, but definitely recommend trying it.
— Twitter (@Flynnjamm)

This project is about a week old and has 14k stars on GitHub already. They call it an 'Open-source orchestration for zero-human companies'. What do you think?
— Reddit r/openclaw

I wanted to use Paperclip with OpenClaw but you have to choose a specific model — the gateway integration isn't available yet.
— Facebook OpenClaw Users

OpenClaw gateway adapter — A new gateway-only OpenClaw flow replaces the legacy adapter. It uses strict SSE streaming, supports device-key pairing.
— OpenClaw Discord

Frequently Asked Questions

What is Paperclip and how does it relate to OpenClaw?

Paperclip is an open-source platform for running 'zero-human companies' — it orchestrates teams of AI agents with org charts, budgets, and governance. OpenClaw serves as the agent runtime, while Paperclip is the management layer that coordinates multiple agents toward business goals.

Do I need Paperclip to use this adapter?

Yes. The adapter is specifically designed to bridge Paperclip's orchestration layer with OpenClaw gateways. Without Paperclip, there's nothing for the adapter to connect. If you just want OpenClaw, you don't need this plugin.

Why is the version number a date (2026.318.0)?

Paperclip uses calendar-based versioning (CalVer) where the version reflects the release date. 2026.318.0 means it was released around March 18, 2026. This is common in rapidly-iterating projects where semver minor/patch numbers would climb very fast.

Can Paperclip work with agents other than OpenClaw?

Yes. Paperclip's tagline is 'if it can receive a heartbeat, it's hired.' It supports OpenClaw, Codex, Claude Code, Cursor, and potentially any agent that can receive task instructions. The OpenClaw adapter is just one of several runtime bridges.

Is the gateway integration fully working?

The latest adapter (2026.318.0) uses a new gateway-only flow with strict SSE streaming and device-key pairing. Earlier community reports noted it wasn't available yet, but the current release appears functional. Check the Paperclip Discord for real-time status.

How does budget enforcement work across OpenClaw agents?

Budget enforcement is handled by Paperclip, not OpenClaw. Paperclip tracks token usage per agent and pauses agents when they hit their monthly budget limit. The adapter reports usage back to Paperclip for tracking, but OpenClaw itself has no budget awareness.

Configuration Examples

Basic Paperclip + OpenClaw setup

# In Paperclip's docker-compose.yml:
services:
  paperclip:
    image: paperclipai/paperclip:latest
    ports:
      - "3000:3000"
    environment:
      - OPENCLAW_GATEWAY_URL=ws://openclaw:18789
      - OPENCLAW_GATEWAY_TOKEN=your-token
  openclaw:
    image: openclaw/openclaw:latest
    ports:
      - "18789:18789"

Multi-agent company setup

# Paperclip agent configuration:
agents:
  ceo:
    runtime: openclaw
    gateway: ws://localhost:18789
    role: CEO
    budget: { monthly: 100 }
  engineer:
    runtime: openclaw
    gateway: ws://localhost:18789
    role: Engineer
    budget: { monthly: 200 }
    agentId: coder

Installation

openclaw plugins install @paperclipai/adapter-openclaw-gateway