Feature request: Cross-session visibility in desktop app

Summary

One Claude Code session/window should be able to see what's happening in another session — e.g., which files are being edited, what tools are running, test results, and current status. Currently, each session operates in complete isolation with no awareness of sibling sessions.

Use case

When running parallel sessions (e.g., in git worktrees or separate terminal tabs), there is no way to coordinate or even know what another session is doing without manually switching between windows/tabs. This makes it easy to create conflicts — two sessions editing the same file, running redundant tests, or working at cross purposes on related code.

Current workarounds (all limited)

• Agent Teams (/agents): Experimental, with rough edges — not yet a reliable coordination mechanism
• Session transcripts on disk: Written to ~/.claude/projects/ but not real-time; require manual inspection and parsing
• Web /tasks endpoint: Only works for cloud-spawned sessions, not local desktop/CLI sessions

None of these provide live, bidirectional awareness between concurrent local sessions.

Proposed ideas (non-prescriptive)

• Shared event bus or local state store between sessions — a lightweight IPC mechanism (e.g., Unix domain socket, SQLite WAL, or named pipe) that broadcasts session activity
• Sidebar/dashboard in the desktop app showing live activity from other active sessions — file being edited, tool in progress, recent output summary
• MCP-based coordination layer — an MCP server that each session connects to, exposing session state as resources and enabling cross-session tool calls
• Session status broadcasting — each session emits structured events (file open/edit, tool invocation start/end, test pass/fail, error encountered) that other sessions can subscribe to

Additional context

This would be especially valuable for users working with git worktrees or multiple feature branches simultaneously, where parallel Claude Code sessions are a natural workflow. Visibility across sessions would reduce conflicts, avoid duplicated work, and enable smarter coordination — whether manual or automated.

---

🤖 Generated with Claude Code