Repository navigation
Replies: 5 comments 1 reply
|
+1. My main use would be a flag: mark a thread to come back to without pinning it, and show only flagged threads with one click. If tags get a sidebar filter, a built-in "flagged" tag with a one-key toggle (thread context menu and a keybinding) would cover it. |
|
Biggest thing for me is separating the tight coupling of repo and project as many tasks I ask agents to do span multiple repos, and I also rely on monorepos which also doesn't help. And I'm currently running all my chats through a repo that contains all my agent tools and allows me to do any task across any repo, MCP, API, or SSH connection all in one agent prompt. With 100 repos like I have, you need the ability to scale out, and to do that, you need a centralized location with all your settings and configs. That's why I agree we need some sort of gmail-label/tag system that we can use to organize thread by project and not by repo. P.S. Everything I do gets documented in a repo somewhere. I don't care where, and I can't keep track of it. If I had to add all 100 repos to T3 Code, I'd be unable to manage it. I don't wanna have to remember some random AI-generated repo project name or select that kinda stuff when I start a task either. |
|
I was thinking about this for a while now. |
|
Note 🤖 Claude Opus 5.5 responding on behalf of Guria A concrete use for the MCP part: skills that run a workflow, like The tag storage from #29053 already covers most of this. The agent side needs a tag action on |
|
Ran into this myself. One project of mine has threads for a few different pieces of work, and I wanted to filter them by which work they belong to. Settling doesn't help since that work isn't done yet. So I went ahead and built it: #36187. If it's useful, great. If you'd rather do it differently, I'm happy to change it or just close it. |
Uh oh!
There was an error while loading. Please reload this page.
#29053 added tags to threads. A thread can carry several, tags survive forks, and tagging doesn't reorder lists. Right now the only use is a config-only filter that hides tagged threads while recording. I'd like to use tags day to day to organize work, the way labels work in email.
Proposal
reviewthreads.The existing hide-while-recording setting stays as it is. Hidden tags would just be one kind of tag.
Why
Projects and pinning don't cover how I actually group work. A single project has threads about different areas (
auth,mobile), different states (waiting-on-review,later), and threads tied to one effort that spans several projects. A thread can belong to more than one of these at once, so folder-style groups like #11998 and #22283 don't fit.Related: #6902, #11998, #22283, #27502
🤖 Claude Opus 5.5
All reactions