Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Feature: Multi-session coordination — allow Claude Code sessions to communicate [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#47997•Fetched 2026-04-15 06:36:19
View on GitHub
Comments
2
Participants
2
Timeline
7
Reactions
0
Author
r0d3l1r0d3l1
Participants
github-actions[bot]github-actions[bot]r0d3l1r0d3l1
Timeline (top)
labeled ×4commented ×2closed ×1

Fix Action

Fix / Workaround

Current workarounds

RAW_BUFFERClick to expand / collapse

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

extent analysis

TL;DR

Implementing a shared task board or inter-session messaging system can help coordinate multiple Claude Code sessions across different repositories.

Guidance

  • Explore the proposed solutions, prioritizing a shared task board to enable read/write access to a shared task list with status updates across linked projects.
  • Consider implementing inter-session messaging using a SendMessage-like tool to target other running sessions by name or ID.
  • Evaluate the feasibility of a session orchestrator to centrally manage and coordinate multiple child sessions.
  • Assess the potential of an MCP-based bridge as a pub/sub message bus between sessions, if an official MCP server is available.

Example

No specific code snippet is provided, as the issue focuses on high-level feature requests and workarounds.

Notes

The current workarounds, such as file-based handoffs and manual relays, do not scale beyond two sessions, emphasizing the need for a more robust solution.

Recommendation

Apply a workaround, specifically exploring the proposed shared task board solution, as it seems to be the most preferred and potentially effective approach to address the issue of coordinating multiple sessions across different repositories.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#database connection#vector store#embedding generation#cache error#pipeline error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Feature: Multi-session coordination — allow Claude Code sessions to communicate [2 comments, 2 participants]