[Feature]: Multiple Spaces for organizing projects and threads (Arc/Zen-style)

[dafzthomas]

Before submitting

• I searched existing issues and did not find a duplicate.
• I am describing a concrete problem or use case, not just a vague idea.

Area

apps/desktop

Problem or use case

When working across many projects (work, side projects, open-source contributions, experiments), the sidebar becomes a long flat list of projects and threads with no way to separate them by context. Switching between a work project and a side project means scrolling through an undifferentiated list, which slows navigation and adds cognitive overhead — especially once you have 10+ projects open.

Proposed solution

Introduce Spaces — named, switchable groups that each contain their own set of projects and threads. Similar to how Arc Browser and Zen Browser handle this:

• A Space switcher in the sidebar (e.g. vertical icon strip or tabs at the top) to move between spaces like "Work", "Side Projects", "OSS", etc.
• Each Space shows only its own projects and threads, keeping the sidebar clean and focused.
• Users can create, rename, reorder, and delete Spaces.
• Projects can be moved or assigned to a Space (drag-and-drop or right-click context menu).
• A keyboard shortcut to cycle between Spaces (e.g. Cmd+1/Cmd+2 or Ctrl+1/Ctrl+2).
• New projects default to the currently active Space.

Why this matters

Power users and professional developers often juggle many projects across different contexts (employer work, freelance, personal). Without a way to group them, the sidebar becomes cluttered and hard to navigate. Spaces would let users maintain focus within a context and switch cleanly between them — a UX pattern that Arc and Zen have proven works well for exactly this kind of multi-context workflow.

Smallest useful scope

Named Spaces that each hold their own project list, with a simple switcher in the sidebar to move between them. No need for per-Space theming, profiles, or separate provider configs in a first pass — just scoped project/thread visibility.

Alternatives considered

• Collapsible folders/groups in the sidebar — lighter weight but doesn't provide the same clean context-switching UX; the sidebar still shows everything at once.
• Multiple windows — related issue [Feature]: Pull a project into a new window #2267 covers pulling a project into a new window, which helps but doesn't solve the organizational problem within a single window.
• Manual naming conventions — prefixing project names with context (e.g. [Work] my-app) is fragile and doesn't scale.

Risks or tradeoffs

• Adds state management complexity (persisting Space assignments, active Space, ordering).
• Need to decide what happens to unassigned/new projects — a sensible default (e.g. a "Default" space or the active space) keeps onboarding simple.
• Should consider whether threads are Space-scoped or project-scoped (projects already imply a grouping for their threads, so Space-scoping projects likely suffices).

Examples or references

• Arc Browser Spaces — vertical Space switcher on the left edge, each Space has its own tabs, bookmarks, and pinned sites.
• Zen Browser Workspaces — similar concept with workspace switching.
• VS Code's multi-root workspaces and JetBrains' project groups solve a related problem in IDEs.

Contribution

• I would be open to helping implement this.

[jacqueslctz]

As a backend dev, I typically have tickets spanning across multiple micro-services to be considered feature complete. So having the ability to better group my sessions would be amazing. Currently I use Warp with colour coded tabs to help with this.

[denny64]

+1 Would love this!!

[bzbetty]

Love it, although I'd want the option to see multiple workspaces at once.

[mackinleysmith]

I think in the sidebar v2 world this is even more relevant than before. I would imagine a large swath of T3 Code's userbase is on company provided computers and having a hard separation of work vs personal projects is imperative. The inbox view of things is amazing but would synchronize and display work front-and-center that I don't want on my company computer.

[troabrea]

This will be great! Much needed

[nhangeland]

+1

[ChristianEllehammer]

+1

[zachback64]

A smaller version of this that I've been using in a local build: plain nested folders for projects in the sidebar. All folders stay visible at once (the "see multiple workspaces at once" case above), and you collapse the ones you don't care about right now.

• Right-click a project, then Move to folder, then pick a folder or create one.
• Folders can nest (Services / Docs), collapse, be renamed, reordered, and deleted. Deleting a folder moves its contents up one level.
• Organization only. Nothing about projects, threads, or agents changes.

Move to folder	Nested folders

Demo projects only. Full-resolution video

Two honest limits: I built it on the per-project (legacy) sidebar, and folder state lives in local UI storage, so it doesn't sync to other devices or mobile. A real version would need the folder list in synced settings and a decision on how it fits Sidebar V2.

If a smallest useful scope would help, I'd suggest: one level of named folders, assigned from the project context menu, stored in synced settings, shown on web and desktop first. Happy to open a small PR for that if you want it.

[mattheworiordan]

would imagine a large swath of T3 Code's userbase is on company provided computers and having a hard separation of work vs personal projects is imperative

Yes, this is exactly my flow. I have separate Claude Work and Claude Personal setups, and creating a clear separation is pretty critical.

A smaller version of this that I've been using in a local build: plain nested folders for projects in the sidebar

@zachback64 this is largely what I was hoping for. Exactly like Claude Desktop offers, you can assign conversations to groups. See screenshot below.

The only downside to this approach is how you can easily see what your most recent conversations are, they got lost in the groups. Personally I think that the folder (group) view is hugely powerful, allows me to work on project based work, as opposed to force myself to work based on git repos/underlying folders which does not actually represent what is going on in my work.

I think what would be a game changer on top of this (missing from Claude desktop) is just an overview page, showing recents, things waitin gon my input, etc. so that I navigate with Groups, but can check in to see what I've forgotten about etc.

[nguyenphutrong]

Hey! I built a version of this in my fork and wanted to check with you before opening a PR.

How it works:

• Dots at the bottom of the sidebar switch between Spaces (or Ctrl+1–9). The grid icon shows everything.
• Projects belong to a Space and their threads follow along. You can also move a single thread on its own.
• There's an overview where you drag projects between Spaces, and create, rename, or delete them.
• Each Space can have its own theme, or just use the app theme.
• Spaces are saved per device, not synced.

It touches web, desktop, and mobile, plus a small server change so thread search can be limited to the current Space. It's a fairly big diff, so I'm happy to split it (web/desktop first, mobile later) or drop parts like the themes.

Is this a direction you'd take? If so, I'll clean it up and open a PR.

[stevebaxter]

This would be really useful. I have a Claude subscription I use for personal stuff. For work we use a private GPU cluster accessed through OpenCode. It is absolutely essential that work data can never go to the Claude servers, I need a clear and complete separation between the two.

So for me this would need to go a bit further - switching "spaces" would switch the full configuration, threads, history etc.

[pedrozimmermannsoares]

+1. T3 Code is now my main app for agent work, and the sidebar is the one part that slows me down. I run two Claude accounts (work and personal) across 9 projects. Today the only way to tell them apart is a name prefix and the 16px icon color.

Named project groups in the new sidebar would solve this without switching back to the legacy sidebar, which loses the newer features. A color per group or per project (#6705) would make the split readable at a glance.