cccp

cccp — Claude Code channels peer

Languages: English (this file) · 한국어

A Claude Code plugin that lets multiple Claude Code instances talk to each other: delegate work to a peer, get a reply back, and optionally relay tool-approval prompts across sessions. Each session runs a local MCP channel server (cccp-inbox); other instances auto-discover it through ~/.cccp/registry/; messages arrive in the receiving Claude's context as <channel source="cccp-inbox" sender="..." kind="..." task_id="..."> tags.

Requirements: Claude Code v2.1.80+ (v2.1.81+ for permission relay), Bun 1.x, macOS or Linux.

Research preview: custom channels are not on the approved allowlist, so sessions must be launched with --dangerously-load-development-channels.

Interactive mode only: channel-driven turns require an interactive claude session. -p/headless mode receives the notification but does not trigger a new model turn — see Limitations.

---

Install

Prerequisites

• macOS or Linux on darwin-arm64, darwin-x64, linux-x64, or linux-arm64
• Either a prebuilt binary from the GitHub release or Bun 1.x on PATH (the wrapper compiles a binary on first run)
• Claude Code v2.1.80+

Option A — install as a Claude Code plugin (recommended)

# inside Claude Code
/plugin marketplace add yusa-imit/cccp
/plugin install cccp@cccp

On the first session that launches the MCP server, server/start.sh resolves a runtime binary in this order:

1. $CCCP_BIN if set
2. server/dist/cccp-inbox-<os>-<arch> (downloaded release asset)
3. server/dist/cccp-inbox (locally compiled)
4. If bun is on PATH, compile one now (one-time, ~5s)
5. Otherwise, fail with a curl command to fetch the release asset

To skip the bun-compile step, drop a prebuilt binary in place:

PLATFORM=darwin-arm64    # darwin-x64 | linux-x64 | linux-arm64
PLUGIN_DIR="$HOME/.claude/plugins/cache/cccp/cccp"     # adjust if version differs
mkdir -p "$PLUGIN_DIR"/*/server/dist
curl -L -o "$PLUGIN_DIR"/*/server/dist/cccp-inbox-${PLATFORM} \
  https://github.com/yusa-imit/cccp/releases/latest/download/cccp-inbox-${PLATFORM}
chmod +x "$PLUGIN_DIR"/*/server/dist/cccp-inbox-${PLATFORM}

Option B — local clone

git clone https://github.com/yusa-imit/cccp.git
# inside Claude Code (from any project)
/plugin marketplace add /absolute/path/to/cccp
/plugin install cccp@cccp

Option C — bare MCP server (no slash commands / skill / hook)

git clone https://github.com/yusa-imit/cccp.git

Add to ~/.claude.json or a project .mcp.json:

{
  "mcpServers": {
    "cccp-inbox": {
      "command": "/absolute/path/to/cccp/server/start.sh"
    }
  }
}

Launching with channels enabled

Every claude invocation that wants channel delivery needs the development-channel opt-in:

# plugin install (Options A/B)
claude --dangerously-load-development-channels plugin:cccp@cccp

# bare MCP server (Option C)
claude --dangerously-load-development-channels server:cccp-inbox

The flag is required while channels are in research preview.

Building binaries yourself

cd server
bun install
bun run build              # current platform → dist/cccp-inbox
bun run build:all          # all 4 supported platforms

The GitHub Actions workflow at .github/workflows/release.yml builds and attaches all four binaries to a Release whenever a tag matching v* is pushed.

---

Run (two-instance scenario)

Terminal 1 — alice

CCCP_NAME=alice claude --dangerously-load-development-channels plugin:cccp@cccp

When the session boots, ~/.cccp/registry/alice.json is written and the inbox HTTP server starts listening on an OS-assigned port.

Terminal 2 — bob

CCCP_NAME=bob claude --dangerously-load-development-channels plugin:cccp@cccp

The two instances now discover each other.

First exchange

In alice's session:

/cccp-peers

Alice calls list_peers and shows bob.

/cccp-delegate bob find the 3 most recently modified files in this directory and tell me their names and mtimes

Alice sends a task message to bob. The following tag arrives in bob's context:

<channel source="cccp-inbox" sender="alice" kind="task" task_id="alice-...">
find the 3 most recently modified files ...
</channel>

Bob's Claude auto-loads the cccp-protocol skill, executes the request, then calls respond_to_peer({ task_id, content }). The result lands in alice's context as <channel ... kind="reply" task_id="...">, and alice's Claude summarizes it for the user.

---

Environment variables