[FEATURE] an intent-recognition and task-routing layer for Claude Code, plus multi-workspace support

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

I've been using Claude Code for over a year. Running many tasks in parallel is where the current workflow still has the most room to improve.

I work on several projects at once, and today one session maps to one task. As a result:

• I keep many windows and terminals open and constantly switch between them.
• I have to remember where each session is and how far along it got.
• When a new idea comes up, I first have to decide which session it belongs to, then go find that session.

The more sessions there are, the higher the overhead, and the more attention it takes away from the actual work. The burden of session management currently falls entirely on the user.

Proposed Solution

1. An intent-recognition layer before execution

• Single entry point: I submit tasks in one place, without first deciding which session should handle them.
• Automatic recognition and routing: the system identifies the intent, decides whether the task belongs to an existing session or needs a new one, and dispatches it automatically.
• User stays in control: I can still open any session at any time to check progress or continue the conversation inside it. When the system is unsure where a task belongs, it should ask me instead of guessing, and I should be able to re-assign a task manually.

In short: let Claude Code manage the sessions, instead of the user.

2. Multi-workspace support

My work spans different kinds of spaces, for example:

• Design: design files made in Pencil
• Requirements: organizing and managing requirements
• Code: the actual development work

I'd like Claude Code to manage multiple workspaces at once, create and maintain projects within each, and have the routing above work across workspaces. For example, a task like "update the home page to match the new design" should be linked to both the design workspace and the code workspace.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Interactive mode (TUI)

Use Case Example

I have three projects running with about six sessions in total. A new idea comes up. Today I have to work out which session it belongs to and find it. With this feature I would type it once into a single entry point. The system would route it to the right existing session, or open a new one, and I could still open any session to see its progress.

Additional Context

A single Claude Code session is already very capable. If the next step is taking over the coordination of many sessions, projects, and workspaces, it would be a step change for heavy users.

Related issues: this request builds on existing ones but goes one step further.

• #29086 (session orchestration and visibility across local sessions)
• #97746 (Agent view: sending one prompt to multiple sessions)
• #95554 (orchestrator view for tasks spawned from a plan session)
• #47983 (multi-project workspace support)

Those focus on cross-session communication, visibility, and multiple code directories. This issue asks for something different: the system decides which session a new task belongs to, so the user no longer has to, and this decision works across workspaces of different kinds (design, requirements, code), not only multiple code directories.