[Feature]: Add global thread filters to the Projects sidebar #6696
jjjjjjjjjjjjjjjjacob
started this conversation in
Ideas
Replies: 2 comments
|
Working demo here: https://github.com/jjjjjjjjjjjjjjjjacob/t3code/tree/feat/sidebar-filters Screen.Recording.2026-03-13.at.2.24.49.PM.mov
|
0 replies
|
Just updated my working demo to the most recent version, can confirm it works with the Claude Code updates.
|
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.
Uh oh!
There was an error while loading. Please reload this page.
Before submitting
Area
apps/web
Problem or use case
The Projects sidebar already shows useful thread state visually, but once there are many threads across multiple projects it becomes hard to narrow the list to the ones I actually need to act on.
Today I can see statuses like working, pending approval, awaiting input, completed, and terminal state indicators, but I cannot filter the thread list by those states. That makes it slower to find active work, blocked threads, threads with terminal activity, or threads where I have unsent draft content.
Proposed solution
Add one global filter control to the Projects sidebar that filters thread lists client-side across all projects.
Initial filter groups:
Working,Connecting,Pending Approval,Awaiting Input,Plan Ready,CompletedTerminal open,Terminal runningUnsent draftFilter semantics:
StatusTerminalThe filter control should live in the Projects header next to the existing add-project action. Each multi-option section should have an inline
Allcontrol that selects the whole section and restores the previous subset when toggled back off.This should stay client-only and reuse existing sidebar state rather than adding backend APIs or contracts work.
Why this matters
This makes the sidebar much more usable once a workspace has many threads.
It helps people quickly find:
The immediate benefit is less scanning, less context switching, and faster recovery when returning to an already busy workspace.
Smallest useful scope
The smallest useful version is a single global filter menu in the Projects sidebar for client-side filtering only.
That first pass should include:
Out of scope for the first pass:
Alternatives considered
The current workaround is manual scanning of the sidebar and using thread titles or visual indicators to hunt for the right thread.
A separate sidebar search feature can help with text lookup, but it does not replace state-based filtering. Search and filtering solve different problems and should be able to coexist.
Risks or tradeoffs
This adds some UI and state complexity to the sidebar, so the implementation should stay narrowly scoped.
Main tradeoffs:
Allbehavior needs to be intuitiveKeeping it client-only and limiting it to one global menu helps contain that complexity.
Examples or references
Comparable pattern:
Relevant context for this request:
Contribution
Working Demo
https://github.com/jjjjjjjjjjjjjjjjacob/t3code/tree/feat/sidebar-filters
All reactions