claude-peers-mcp-inter-instance-messaging

Enables Claude Code instances to discover and message each other across terminal sessions.

7|2|Updated May 16, 2026
One-click install
npx skills add https://github.com/reason-machines/mcp-skills --skill claude-peers-mcp-inter-instance-messaging-reason-machines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: claude-peers-mcp-inter-instance-messaging
Source: https://github.com/reason-machines/mcp-skills/tree/main/skills/claude-peers-mcp-inter-instance-messaging
Command: npx skills add https://github.com/reason-machines/mcp-skills --skill claude-peers-mcp-inter-instance-messaging-reason-machines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When running multiple Claude Code sessions across different projects or terminals, the instances are isolated and cannot coordinate, leading to merge conflicts, duplicated work, and missed context. This Skill connects them through a local broker so they can discover each other and exchange messages in real time. ## Core Features & Use Cases - Peer Discovery: List all running Claude Code instances on the machine, in the current directory, or in the same git repository, including their working directory, branch, and work summary. - Real-Time Messaging: Send messages to a specific peer by ID, delivered instantly via the claude/channel protocol, with manual polling as a fallback. - Status Broadcasting: Set a work summary visible to other peers, optionally auto-generated on startup using an OpenAI model. - Use Case: While editing a frontend in one terminal and a backend API in another, ask Claude to list peers in the repo and message the backend instance to confirm whether an endpoint schema changed before writing integration code. ## Quick Start Ask Claude to list all peers on this machine and send a message to the one working in your repository.

Frequently Asked Questions about claude-peers-mcp-inter-instance-messaging

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

FAQPage Schema
How do I let multiple Claude Code instances talk to each other?▼

Install the claude-peers MCP server, register it with claude mcp add at user scope, then start Claude Code with the --dangerously-load-development-channels server:claude-peers flag. Instances register with a local broker and can list peers and send messages.

How to send a message to another Claude Code session?▼

Call the send_message tool with the target peer ID from list_peers and your message text. The message is pushed instantly to the recipient via the claude/channel protocol, and check_messages works as a manual polling fallback.

Does claude-peers work with API key authentication?▼

No, the channel protocol requires claude.ai login and does not work with API key authentication. Run claude login before starting sessions if messages are not arriving.

Why are peers not showing up in list_peers?▼

Check broker registration with bun cli.ts status, verify Claude Code is v2.1.80 or later, and confirm both the --dangerously-skip-permissions and --dangerously-load-development-channels flags are set when starting sessions.

Is claude-peers messaging secure over the network?▼

The broker binds only to 127.0.0.1, so there is no external network access, but any local process can connect and messages are not encrypted. Security relies entirely on the localhost boundary.