[Feature]: Multiple Spaces for organizing projects and threads (Arc/Zen-style) #6733
dafzthomas
started this conversation in
Ideas
Replies: 5 comments
|
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. |
0 replies
|
+1 Would love this!! |
0 replies
|
Love it, although I'd want the option to see multiple workspaces at once. |
0 replies
|
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. |
0 replies
|
This will be great! Much needed |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Before submitting
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:
Cmd+1/Cmd+2orCtrl+1/Ctrl+2).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
[Work] my-app) is fragile and doesn't scale.Risks or tradeoffs
Examples or references
Contribution
All reactions