OpenClaw Gateway
openclawgateway connects Paperclip to an OpenClaw instance over the OpenClaw Gateway WebSocket protocol. Use it when OpenClaw is running on another machine, inside Docker, or behind a shared gateway…
OpenClaw Gateway
openclawgateway connects Paperclip to an OpenClaw instance over the OpenClaw Gateway WebSocket protocol. Use it when OpenClaw is running on another machine, inside Docker, or behind a shared gateway and you want Paperclip agents to delegate work to it.
> Info: openclawgateway is fully functional in the runtime but currently shown as "Coming soon" in the agent-config adapter-type dropdown. It's reached through the OpenClaw invite-prompt flow instead of being picked manually. This page documents the adapter so you can target it via the API or an imported company. Direct UI selection is planned.
---
When To Use
OpenClaw is reachable over ws:// or wss:// (local Docker, remote host, Tailscale). You want a shared OpenClaw instance to serve multiple Paperclip agents. You need device-auth pairing between Paperclip and the gateway.
When Not To Use
The remote agent doesn't speak the OpenClaw Gateway protocol. Use HTTP (/docs/adapters/http). You want to run a headless local CLI agent on the same machine. Use Claude Local (/docs/adapters/claude-local), Codex Local (/docs/adapters/codex-local), or Process (/docs/adapters/process).
---
Transport