Paperclip ACP Runtime Plugin
The runtime that makes /acp spawn actually do something. ACP (Agent Client Protocol) plugin for Paperclip — spawns Claude Code, Codex CLI, Gemini CLI, and OpenCode as stdio subprocesses bound to chat threads. Up to 5 concurrent agents per thread, persistent or oneshot mode, idle and max-age timeouts, and a namespaced cross-plugin event bus that lets Telegram/Discord/Slack drive coding agents from any chat.
ACP (Agent Client Protocol) runtime plugin for [Paperclip](https://github.com/paperclipai/paperclip). Run Claude Code, Codex, Gemini CLI, and OpenCode from any chat platform through thread-bound sessions.
Why this exists
Paperclip's chat plugins (Telegram, Discord, Slack) let users interact with agents through messaging platforms, but they need a runtime to actually spawn and manage coding agent processes. The ACP plugin is that runtime — it bridges chat messages to subprocess-managed coding agents over stdio, following the [Agent Client Protocol](https://agentclientprotocol.com/) standard from Zed Industries.
Without this plugin, the /acp spawn, /acp status, and /acp close commands in the chat plugins have nothing to connect to.
Agent lifecycle
Spawn agents as subprocesses over stdio Persistent sessions stay alive for follow-up prompts in the same thread Oneshot mode auto-closes after a single task Idle timeout — close after 30 min of inactivity (configurable) Max age — close after 8 hours regardless of activity (configurable) Graceful shutdown — SIGTERM with cleanup of thread bindings
1:N session support
A single chat thread can run up to 5 concurrent agent sessions (configurable via maxSessionsPerThread) — Claude Code reviewing while Codex implements, for example. Routed by session ID. acpstatus lists active sessions with uptime, idle time, binding info.
Supported agents
| Agent | Command | |---|---| | Claude Code | claude | | Codex CLI | codex | | Gemini CLI | gemini | | OpenCode | opencode |
Shared by Matt Van Horn