Feature: Multi-session coordination — allow Claude Code sessions to communicate

## Problem

When working on tasks that span multiple repositories, I run separate Claude Code sessions in each repo. Currently there's no way for multiple sessions to:

• Send messages to each other
• Share a task board or status updates
• Monitor progress across all sessions from a central session

The user becomes the manual router between all sessions, copy-pasting status updates back and forth.

## Use case

Real-world example: I'm deploying a networking resource in an infrastructure repo (Session A), waiting to use it for a database import in an application repo (Session B), while also configuring a consuming service in a third
repo (Session C). Each session is blocked or unblocked by progress in the others, but none of them know about each other. I had to manually relay every status update between all of them.

This pattern is common in any multi-repo architecture: platform teams, monorepos with shared dependencies, microservices that need coordinated changes, etc. The more sessions involved, the harder it is to keep them in sync
manually.

## Proposed solutions (in order of preference)

1. Shared task board — all sessions in linked projects can read/write to a shared task list with status updates
2. Inter-session messaging — a SendMessage-like tool that targets other running sessions by name or ID
3. Session orchestrator — a central session that can spawn, monitor, and coordinate multiple child sessions
4. MCP-based bridge — an official MCP server that acts as a pub/sub message bus between any number of sessions

## Current workarounds

• File-based handoff via shared markdown files (e.g., next-session-prompt.md, memory files)
• User manually relays status between sessions
• /loop skill polling for file changes (hacky)
• None of these scale beyond two sessions

## Environment

• Claude Code version: 2.1.92
• Model: Claude Opus 4.6 (1M context)
• OS: macOS Darwin 25.3.0 (Apple Silicon)
• Shell: bash 3.2

---

This issue was drafted collaboratively with Claude Code itself, which suggested the feature while we were working across multiple sessions. *This issue was drafted collaboratively