Feature Request: Multi-Agent Coordinator / Conference Room Mode

Problem

Power users running multiple Claude Code sessions in parallel (via VS Code extension) face a UX challenge: there's no easy way to distinguish between sessions or route conversations to the right context. Currently, if you have 5+ sessions working on different aspects of a project, you have to manually switch windows and remember which session is handling which task. Talking to the wrong session creates confusion for both the user and Claude.

Proposed Solution: "Conference Room" Mode

A single input interface that acts as a coordinator across multiple agent sessions:

┌─────────────────────────────────────────┐
│           CONFERENCE ROOM               │
│         (Single input point)            │
└─────────────────┬───────────────────────┘
                  │
         ┌────────▼────────┐
         │   COORDINATOR   │
         │  (Routes input) │
         └────────┬────────┘
                  │
    ┌─────────────┼─────────────┐
    │             │             │
┌───▼───┐   ┌─────▼─────┐   ┌───▼───┐
│ Bob   │   │  Alice    │   │ Carl  │
│ (GUI) │   │ (Engine)  │   │ (Bugs)│
└───────┘   └───────────┘   └───────┘

How it would work:

1. Single input interface - User speaks into one "room"
2. Coordinator agent - Understands project domains and routes input to the appropriate session
3. Named sessions/agents - Each session has a name and domain ownership (e.g., "Bob handles GUI", "Alice handles backend engine", "Carl handles bugs")
4. Dynamic spawning - When a new issue arises outside existing domains: "That's a new area, let's bring in Dave" → new session spawns and joins the "meeting"
5. Shared context - All agents have awareness of the overall project, but stay focused on their domain

Use Case

When building complex applications, I regularly run 5+ Claude Code sessions simultaneously in VS Code:

• Main feature development
• GUI / frontend work
• Backend / engine changes
• Bug fixes (spawned when discovered)
• Refactoring tasks

Currently I get confused about which session is which. I end up talking about an issue in the wrong session, which confuses Claude until I clarify.

Benefits

• No more "wrong window" conversations
• User stays in architect/product owner mode
• Parallel execution with clear responsibility
• Natural handoffs between domains
• Scales with project complexity

Current Workarounds

• Window positioning on screen
• Starting each session with context reminders
• None of these scale well

Related Issues

This is complementary to #19555 (Dynamic Thought Bubble Windows) - that issue addresses visibility into parallel tasks, while this proposal addresses coordination and routing across sessions.

---

Submitted via Claude Code - this feature request emerged from real usage patterns.