Workspaces: group threads by context (Office / Research / Dev / Notes), like Chrome tab folders

[MdSadiqMd]

The problem, as a day in my life

I live in T3 Code across four very different modes, often on the same day:

• Office work — status updates, planning, admin-y back-and-forth.
• Research — long exploratory threads where I'm reading, comparing, and thinking out loud.
• Development — actual building, PRs, debugging.
• Quick notes — fast "capture this before I forget" chats with Claude Code.

Right now all of these live in one flat list of threads. With a handful of threads it's fine. But the moment the number of active threads grows, I lose the plot: a research thread sits three rows above a throwaway note, which sits above a live dev thread with an open PR. There's no sense of context — of which world a thread belongs to — so I spend real energy just re-finding where I was.

What I want

Think Chrome tab folders / tab groups, but for T3 threads: a way to group threads into named workspaces (e.g. Office, Research, Dev, Notes), so each mode stays separated and self-contained.

The key properties that would make this a life-saver:

• Separation — threads are organized by the world they belong to, not one undifferentiated list.
• Context persistence / "remind-full" — when I open a workspace, it reminds me what I was doing there: the threads in it, where I left off. Switching workspaces switches mental context cleanly.
• Scales with activity — this is "nice" at 5 threads and essential at 30. As active threads increase, workspaces are what keep the whole thing usable instead of overwhelming.

Why it matters

The value compounds with the number of active threads. A flat list degrades linearly (actually worse) as work piles up; grouped workspaces keep each context small and legible no matter how much total work is in flight. For anyone using T3 Code as a daily driver across multiple kinds of work, this is the difference between "I can find my stuff" and "I dread opening the app."

Happy to discuss scope, naming (workspaces vs. groups vs. folders), and how deep the "reminds me where I left off" behavior should go — starting from something as light as named, collapsible groups would already help a lot.

Not the old tabs feature (important distinction)

This might sound like the old tab feature we used to have, but that's not what I'm asking for. The old model tucked things away — "this is in archive mode," "this tab is different / hidden" — and the problem is that out of sight becomes out of mind. My research work in particular gets ignored the moment it's not visible, and I don't want that.

What I want instead:

• Still visible, not archived. Workspaces should keep their threads present, so I don't mentally write off research as "stashed somewhere I'll never look." The grouping organizes; it doesn't bury.
• Filterable, so the surface stays calm. I don't want dozens of things lying around at once, but I also don't want them gone. The answer is filtering: narrow to one workspace (or a few) when I want focus, and bring the rest back into view whenever I want. Nothing is lost, nothing is hidden by default — I just control how much is on screen.

So: group + keep visible + filter, rather than group + archive + hide.

[Ryner01]

I would love to have this too. Even if you are multitasking having some organisation between threads is very useful