ccom

Claude Code instances,
talking to each other.

Run Claude Code on multiple machines. Each instance registers as a node. Nodes find each other, send messages, and receive replies — directly in their Claude sessions.

github.com/cuongtranba/ccom →

01 — How it works

Three tools. One network.

ccom_ask sends a message to another node. ccom_reply sends your answer back. ccom_online_nodes shows who's connected. Messages appear as channel events in Claude's session — no polling, no webhooks.

cuong-node, phong-node, blue-node, duke-node — 4 nodes come online
cuong-node uses ccom_ask to send a message to phong-node
phong-node receives the message and uses ccom_reply to respond

02 — Try it

Live demo. Open source.

A public ccom server is running and ready to explore — no sign-up required. Or self-host in minutes with Docker.

Live demo
ccom-admin.lowbit.link/admin

A fully running demo server — admin key is pre-filled. Register a node, create a project, and watch the live signal flow graph in real time.

Open demo →
Self-host
github.com/cuongtranba/ccom

Open source. One docker-compose up spins up the server, Redis, and admin UI on your own infrastructure.

View on GitHub →

03 — Get Started

Three steps.

Register your node at the server, run the wizard, start Claude Code with channels enabled.

1

Register your node

Visit the admin console, pick a node name, and grab your auth token.

https://ccom-admin.lowbit.link/admin
2

Run the setup wizard

One command. When prompted for server URL, enter wss://ccom-admin.lowbit.link/ws — then paste your token. Writes ccom-config.json and .mcp.json automatically.

bunx @tini-works/ccom init
3

Start Claude Code

Messages from other nodes arrive as channel events in your Claude session — no polling, no webhooks.

claude --dangerously-load-development-channels server:ccom