[Feature]: Thread grouping / filtering

[gmmeyer]

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

I frequently have projects that end up spanning multiple threads. for example, I will review the same project with claude and codex, or I will have a new thread after to monitor a rollout.

I want to be able to group these and filter them together, so I can see them all in one place and see the full history.

Proposed solution

Threads should have metadata based tags, both human and AI generated. At each human input turn a cheap model should check it out and auto assign new tags if needed. They should be done datadog style so a thread tagged branch:greg/my-project can be grouped together with "branch"

New threads should then also inherit the tags from the old thread if you create a new thread using the new thread on branch tool.

Why this matters

Right now I have 15 threads open, one project has two different threads, it would be nice to group them together. Perhaps my usage is a little odd, but I think this is a great solution for the problem of structured search in general. Tags are a great way to do this kind of semi structured search data.

Smallest useful scope

Just add tags and let us search on them. I'd love to be able to group on them too. I think it's actually a fairly big change (sorry theo!).

Alternatives considered

Generally, unstructured search is nice but doesn't allow grouping, and because it's unstructured and (at least for me) I don't always remember what the name of a branch was, it's much harder to find the two or three threads that were all for the same feature or bug.

Risks or tradeoffs

I think the biggest risk is that the AI generated tags may end up being shitty and it would be better to do it in a more structured way, just group by branch and human generated for example.

Examples or references

I have a mostly complete first pass here, I was going to submit a PR but the instructions said not to unless invited, so I submitted an issue instead: https://github.com/gmmeyer/t3code/tree/agent/thread-tags-beta

Contribution

• I would be open to helping implement this.

[gmmeyer]

a common workflow that would benefit from this:

I build a feature with Codex
I open a new thread with Claude to review my feature

These are not the same thread, but should be grouped together, at least optionally so

[Exotic209093]

This would be quite cool, the chat is purely a convosation and the claude and sol comunitcate across it big feature but very intresting if done right

[kendyl93]

Use case: one product feature delivered across several repos

My work is split across several repos, each added as its own T3 Code project:

• a shared npm package I maintain
• a microfrontend that uses that package
• a host app that loads the microfrontends

The product team thinks of a feature as one thing, but delivering it often means changes in two or three of these repos. In T3 Code that turns into several chats in different projects, with nothing connecting them. I have to remember which chats belong to the feature and look for them project by project.

Ask: a way to group threads by feature across projects. Two possible shapes:

1. Tags. Tag each thread, e.g. feature:checkout-redesign, and filter the sidebar by tag to see every matching thread from all projects, each labelled with its project.
2. Feature rooms. A named room that sits alongside projects and collects threads from any project.

Either one solves it. The key requirement is that a group can include threads from more than one project.

This is different from #11998 (groups inside one project) and #6733 (grouping whole projects).