[FEATURE] Multiple independent chat threads in Cowork Dispatch

[canberkdoger]

Preflight Checklist

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

Problem Statement

Currently, Dispatch only supports a single chat thread. When working on multiple unrelated tasks (e.g., researching a topic while managing files), all conversations pile into one thread. This causes the context window to fill up with unrelated information, degrading response quality and making it hard to maintain focused workflows.

Proposed Solution

Allow opening multiple independent chat threads within Dispatch, each with its own isolated context. A simple tab/sidebar UI would let users switch between threads without cross-contamination.

This would significantly improve productivity for users who juggle multiple parallel workstreams in Cowork.

Alternative Solutions

Restarting sessions loses all context. Opening multiple Claude Desktop instances doubles memory usage. Neither provides a seamless multi-thread experience within Dispatch.

Priority

High - Significant impact on productivity

Feature Category

Interactive mode (TUI)

Use Case Example

1. I ask Dispatch to research flight options for an upcoming trip
2. While that's running, I want to ask Dispatch to help organize files in my Downloads folder
3. Currently both tasks share the same thread, so flight research context mixes with file management context
4. With multiple threads, I could have "Travel planning" in one tab and "File cleanup" in another, each with clean, focused context

Additional Context

This is specifically about Cowork Dispatch (the persistent chat interface in Claude Desktop), not Claude Code CLI.

[howermj]

Strong +1 on this. I run multiple Cowork projects under one umbrella (a publishing ecosystem with 7 sub-projects, each as its own Cowork instance). Dispatch is currently unusable for me because there's no way to separate data between projects.

The core need isn't just convenience — it's client/project data separation. If I'm working across projects that require confidentiality boundaries, a single shared Dispatch channel means I can't use the feature at all.

What I'd want:

• Project-level targeting — Dispatch should know which project it's talking to
• Separate chat channels per project — so conversations and context don't bleed across boundaries
• Ideally, the ability to route a Dispatch message to a specific project instance based on context

This is closely related to the broader need for Cowork to treat projects as first-class identity objects rather than just folder paths.

[hungluu]

This is the most wanted feature to me. The context shouldn’t be mixed between my projects and also with my personal non-coding stuffs

[github-actions]

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.