cc-connect-room

You can sync Claude Code sessions across machines by creating a peer-to-peer room. This binds local AI instances to a shared gossip-protocol room, providing a unified chat history and file-drop environment for collaborative debugging.

A P2P chat room is a shared, decentralized space managed by a gossip protocol. It allows multiple Claude Code instances to exchange context, prompts, and file interactions in real-time without relying on a central server.

You join a shared room by using the provided MCP tools to enter a secure ticket. This ticket-based authentication enforces human-in-the-loop consent gates to ensure secure room joining and session management.

Yes, you can use the gossip protocol to share file interactions and prompts between developer machines. It synchronizes the context across different peers, allowing seamless collaborative development on a shared codebase.

Yes, synchronizing Claude sessions requires manual consent. The system enforces human-in-the-loop consent gates during secure room joining to ensure developers explicitly authorize peer connections and session sharing.

The system relies on ticket-based authentication and requires participants to manage room lifecycles manually. You must create, join, list, and leave rooms explicitly, and all peers need active MCP tool access to maintain the shared context.