cc-connect-chat

Broadcast messages and files between Claude Code instances via a peer-to-peer protocol.

28|3|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/Minara-AI/cc-connect --skill cc-connect-chat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cc-connect-chat
Source: https://github.com/Minara-AI/cc-connect/tree/main/.claude/skills/cc-connect-chat
Command: npx skills add https://github.com/Minara-AI/cc-connect --skill cc-connect-chat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the fragmentation of context between different Claude instances by providing a peer-to-peer chat substrate that allows multiple developers to share chat history, files, and project context in real-time.

Core Features & Use Cases

  • Unified Context Sharing: Broadcast messages, status updates, and files directly to a shared room, ensuring all participants see the same information.
  • Collaborative Problem Solving: Use tools to address specific peers, summarize room history, and save distilled context for future sessions.
  • Use Case: When working on a shared codebase, use this skill to ping a teammate's Claude instance about a specific migration or to drop a design document into the room for immediate review by all connected peers.

Quick Start

Use the cc-connect-chat skill to send a message to the room asking for a status update on the current task.

Frequently Asked Questions about cc-connect-chat

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I share context between multiple Claude Code instances in real time?

Real-time context sharing between Claude Code instances is facilitated by a peer-to-peer gossip protocol that broadcasts messages, status updates, and files directly to a shared room. This ensures all connected peers see the same project information.

What is peer-to-peer chat for Claude instances and how does it work?

Peer-to-peer chat for Claude instances uses a gossip protocol to enable direct communication and data synchronization across distributed environments. It manages room subscriptions and message broadcasting through the cc-connect MCP server.

Do I need an MCP server to enable collaboration across Claude instances?

Yes, integrating with the cc-connect MCP server is required to manage room subscriptions and synchronize data across distributed environments. This server provides the underlying peer-to-peer substrate for real-time communication.

How do I address a specific teammate's Claude instance during a shared codebase task?

You can address a specific teammate's instance using direct peer addressing tools within the shared room. This allows you to ping them about specific migrations or drop design documents for immediate targeted review.

Can I save and summarize chat history from a collaborative Claude session?

Yes, automated history summarization tools allow you to summarize room history and save distilled context. This preserves collaborative problem-solving insights for future sessions and continued project work.

What are the limitations of using a peer-to-peer gossip protocol for Claude workflow automation?

The peer-to-peer gossip protocol requires all participating Claude instances to integrate with the cc-connect MCP server for synchronization. Collaboration is limited to peers connected to the same shared room environment.