In multi-repo projects, the most important threads are often not the most recently active ones.
Right now, threads seem to compete mostly on recency. That works for short-lived conversations, but it breaks down when one thread is the main coordination or reference thread for a larger project. In practice, that thread gets pushed down by more active implementation threads and becomes easy to lose in the list.
A pin / unpin thread feature would solve this by letting users manually keep a few important threads at the top of the sidebar, regardless of recent activity.
Why this matters
- In multi-repo work, there is often one “main” thread that coordinates the project across several repo-specific threads.
- That main thread may stay important even when it is not the most recently updated one.
- Without pinning, important long-lived threads get buried by short-term active conversations.
- This makes navigation and project continuity worse.
Suggested behavior
- Add a
Pin thread / Unpin thread action to each thread. - Pinned threads appear in a dedicated section above the normal thread list.
- Pinned threads stay at the top regardless of new activity in other threads.
- Manual ordering inside the pinned section is optional; simple pinned-first behavior would already help a lot.
Example use case
I often work across multiple repositories that belong to the same project. I may have:
- one main planning / coordination thread,
- several repo-specific implementation threads,
- a few temporary debugging threads.
The repo-specific threads become more active and push the main thread down, even though the main thread is the one I need fastest access to. Pinning would make that workflow much easier.
Not the same as archive
This is different from archiving or hiding old threads. The need here is to keep important active reference threads visible, not to remove stale ones.
Potential nice-to-haves
- Keyboard shortcut for pin/unpin
- Pin icon in the thread list
- Limit pinned threads to a small number to keep the sidebar clean
In multi-repo projects, the most important threads are often not the most recently active ones.
Right now, threads seem to compete mostly on recency. That works for short-lived conversations, but it breaks down when one thread is the main coordination or reference thread for a larger project. In practice, that thread gets pushed down by more active implementation threads and becomes easy to lose in the list.
A
pin / unpin threadfeature would solve this by letting users manually keep a few important threads at the top of the sidebar, regardless of recent activity.Why this matters
Suggested behavior
Pin thread/Unpin threadaction to each thread.Example use case
I often work across multiple repositories that belong to the same project. I may have:
The repo-specific threads become more active and push the main thread down, even though the main thread is the one I need fastest access to. Pinning would make that workflow much easier.
Not the same as archive
This is different from archiving or hiding old threads. The need here is to keep important active reference threads visible, not to remove stale ones.
Potential nice-to-haves