mvanhorn

Paperclip Plugin Acp — Communication skill for Claude Code

Communication community

ACP (Agent Client Protocol) runtime plugin for Paperclip - run Claude Code, Codex, and Gemini CLI from any chat platform.

How to install Paperclip Plugin Acp

This entry records only its repository, not the path inside it, so there is no exact command to give. Open mvanhorn/paperclip-plugin-acp and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Paperclip Plugin Acp does

ACP (Agent Client Protocol) runtime plugin for Paperclip - run Claude Code, Codex, and Gemini CLI from any chat platform.

Alternatives in Communication

Lark Coding Agent Bridge — Bot that bridges Feishu/Lark messenger with a local Claude Code or Codex CLI 2.4k ★
Claude Code Webui — Web-based interface for Claude CLI with streaming chat responses 969 ★
Openab — A lightweight, secure, cloud-native ACP harness that bridges Discord and any ACP-compatible coding CLI 321 ★

README

paperclip-plugin-acp

[![npm](https://img.shields.io/npm/v/paperclip-plugin-acp)](https://www.npmjs.com/package/paperclip-plugin-acp) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

ACP (Agent Client Protocol) runtime plugin for [Paperclip](https://github.com/paperclipai/paperclip). Run Claude Code, Codex, Gemini CLI, and other coding agents from any chat platform through thread-bound sessions.

Built on the Paperclip plugin SDK.

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 created by Zed Industries.

Without this plugin, the `/acp spawn`, `/acp status`, and `/acp close` commands in the chat plugins have nothing to connect to.

What it does

Agent lifecycle management

Spawn agents as subprocesses over stdio from any chat platform
Persistent sessions - agents stay alive for follow-up prompts within the same thread
Oneshot mode - single-task sessions that auto-close after completion
Idle timeout - sessions close after 30 min of inactivity (configurable)
Max age - sessions close after 8 hours regardless of activity (configurable)
Graceful shutdown - SIGTERM with cleanup of thread bindings and state

1:N session support

A single chat thread can run up to 5 concurrent agent sessions (configurable via maxSessionsPerThread)
Spawn multiple agents in the same thread - for example, Claude Code reviewing while Codex implements
Route messages to specific sessions by session ID
Active sessions tracked per-thread as an array; closed/errored sessions don't count toward the cap
The acp_status tool lists all active