Adapter Manager
Every agent in Paperclip needs an adapter — the shim that lets the control plane talk to a specific AI runtime. Built-in adapters ship with the product (Claude Code, Codex, Gemini, OpenCode, Cursor,…
The Adapter Manager
Every agent in Paperclip needs an adapter — the shim that lets the control plane talk to a specific AI runtime. Built-in adapters ship with the product (Claude Code, Codex, Gemini, OpenCode, Cursor, Pi, Hermes, HTTP, Process, OpenClaw Gateway), and you can extend the set by installing external adapters from npm or a local path.
The Adapter Manager is the single place where you see which adapters your instance knows about, toggle their visibility in the agent menus, install and upgrade external packages, and pause external overrides on built-ins.
This guide walks through the page itself. For the per-adapter config fields (working directory, model names, timeouts, environment variables) see Agent Adapters (/docs/your-org-agents/agent-adapters). For the technical catalog of every adapter type — wire format, capabilities, model listings — see the Adapter Reference (/docs/adapters/overview).
> Alpha: The external-adapter runtime is in alpha. APIs, on-disk layout, and the list of exposed capabilities can change between versions. For production use, pin adapter package versions.
---
Opening the Adapter Manager
The Adapter Manager lives under Settings → Adapters. The breadcrumb reads Company → Settings → Adapters, and the page header shows a CPU icon, the page title, and an Alpha badge.
!Adapter Manager list (/uploads/content/2026/04/415c9043-3133-43ec-9d74-5556ed956388.webp)
Below the header there's a persistent amber notice reminding you that external adapters are alpha, and that the power icon on each row hides an adapter from the agent menus without removing it.