Overview

Adapters Overview

Adapters connect Paperclip's control plane to the runtime that actually does the work. Use this section when you need to choose an adapter, understand what Paperclip expects from one, or build a new adapter package.

---

What An Adapter Does

Every adapter is responsible for the same core jobs:

Launch or call the underlying runtime. Pass the agent's company, task, and wake context through. Capture results, session state, and usage metadata. Validate the environment before a run starts. Optionally provide a custom UI transcript parser and skills sync behavior.

> Note: Paperclip orchestrates agents. The adapter decides how the runtime starts, how it keeps state, and how its output is interpreted.

---

Choose An Adapter

| Use case | Start here | |---|---| | Claude Code on your machine | Claude Local (/docs/adapters/claude-local) | | OpenAI Codex CLI on your machine | Codex Local (/docs/adapters/codex-local) | | Gemini CLI on your machine | Gemini Local (/docs/adapters/gemini-local) | | Cursor Agent CLI on your machine | Cursor Local (/docs/adapters/cursor-local) | | OpenCode CLI with provider/model routing | OpenCode Local (/docs/adapters/opencode-local) | | Pi CLI with its built-in tool set | Pi Local (/docs/adapters/pi-local) | | Hermes Agent with persistent memory and 30+ tools | Hermes Local (/docs/adapters/hermes-local) | | OpenClaw over a WebSocket gateway | OpenClaw Gateway (/docs/adapters/openclaw-gateway) | | A custom shell command or script | Process (/docs/adapters/process) | | A webhook or cloud service you control | HTTP (/docs/adapters/http) | | A standalone npm package or local plugin | External Adapters (/docs/adapters/external-adapters) | | Writing a new adapter package from scratch | Creating an Adapter (/docs/adapters/creating-an-adapter) | | Building a custom run-log parser | Adapter UI Parser Contract (/docs/adapters/adapter-ui-parser) |