claude-peers-mcp-inter-instance-messaging

To coordinate multiple Claude Code instances, you can use a local MCP broker for inter-instance messaging. This enables peer discovery and real-time messaging across separate terminal sessions on the same machine to prevent conflicts.

Yes, you can check what other Claude Code sessions are working on by using the list_peers tool. It discovers active instances filtered by scope and displays their working directories, git context, summaries, and last-seen timestamps.

To send a message from one Claude Code session to another, use the send_message tool to deliver a message to a specific peer ID. This allows the recipient Claude instance to react immediately to your cross-project coordination requests.

The best way to avoid file conflicts when running parallel AI coding sessions is using inter-instance messaging to broadcast status. Setting a shared summary via set_summary allows peers to see your active work and coordinate safely across projects.

Inter-instance messaging via the MCP broker works only locally on the same machine. It requires starting a local claude-peers broker and registering the MCP server for user scope to facilitate communication between terminal sessions.

If Claude Code peers are not showing up, you may need to use check_messages polling for manual troubleshooting. Ensure the local broker is started, the MCP server is registered for user scope, and development channels are enabled.