vikrantjain

Claude Chat — Communication skill for Claude Code

Communication community

Real-time chat between distributed Claude Code instances via a shared WebSocket broker, built on the experimental Channels API.

How to install Claude Chat

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

What Claude Chat does

Real-time chat between distributed Claude Code instances via a shared WebSocket broker, built on the experimental Channels API.

Alternatives in Communication

HolaOS — Open-source agentic workspace enterprises can make their own 10.9k ★
Gtm Strategy — Create GTM strategy with channels, messaging, and launch timeline 7.8k ★
YouTube To Ebook — Claude skill for turning YouTube transcripts from your favorite channels into EPUB ebooks, delivered to your e 426 ★

README

claude-chat

A Claude Code plugin that lets multiple Claude Code instances chat with each other in real time — across machines, containers, and networks — through a shared WebSocket broker, built on the experimental [Channels API](https://code.claude.com/docs/en/channels).

![Two Claude Code instances coordinating a cross-service contract over the claude-chat channel in real time](demo/claude-chat-demo.gif)

Do you need this?

Claude Code now ships [**cross-session messaging**](https://code.claude.com/docs/en/cross-session-messaging) built in (v2.1.224+, macOS/Linux): `ListAgents` and `SendMessage`, nothing to install, no broker to run. **If your sessions are two terminals on one laptop, use that instead** — it's simpler, it's supported, and it has a real permission model.

`claude-chat` is for the cases the built-in feature doesn't cover:

	Built-in cross-session messaging	`claude-chat`
Setup	none	plugin + one broker + a research-preview flag
Sessions on one machine	yes	yes
Sessions on different machines	reply-only — Claude can answer a message that arrived from another machine, but can't start one; it travels through Anthropic servers over Remote Control	full two-way, any peer can initiate; traffic stays on your own network
Across a filesystem boundary (container ↔ host, remote SSH box)	no — peers are found through files on disk and a per-session Unix socket, so both sides must see the same filesystem	yes — the broker is the only thing both sides need to reach
Broadcast to everyone at once	no — one named recipient per message	yes — omit `to`
Non-Claude participants	no — Claude sessions only	yes — `claude-chat-human` joins as a first-class addressable peer, with join/leave events