Repository navigation
Sidebar: group every section by project, with an optional Working row in each boring folder #33380
GuardedAirplane
started this conversation in
Ideas
Replies: 0 comments
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.
Problem
I run agents in several projects at once. At a glance I want to answer, per project: what is running, what came back and needs me, and what I parked.
The boring sidebar (#21039) already answers part of that: its active list is grouped into project folders. Two gaps remain:
Proposal
My personal preference is to keep threads organized by project, while using the same Done and Working sections as the default sidebar. I want the project organization together with that familiar separation between work that has finished and work that is still running.
The base proposal can stand alone; the second part is an optional extension.
Part 1: Sections by project (base)
A Labs switch, Settings → Labs → Sections by project, off by default.
Part 2: a Working row in each boring folder (optional extension)
Only when Boring sidebar and Sections by project are both on: each project folder keeps its running threads under a collapsible Working N row at the bottom of the folder. Finished threads, and threads that need you, sit above it at the top of the folder.
How this differs from #30980
#30980 asks to bring back the global Working shelf in the boring sidebar: running threads leave their folders for one cross-project Working section above Snoozed and Settled. That answers "what is running across everything?"
Part 2 does the opposite: running work stays inside its project, so a folder answers "where is this project at?" In that mode there is no global Working shelf. The two aren't mutually exclusive, but they pull the boring sidebar in different directions, so it seems worth a maintainer call on which one (or neither) the boring sidebar should have. Part 1 doesn't depend on that decision.
Tradeoffs
Implementations for evaluation
Both were opened without prior approval. They're here so you can see the behavior, not as a request to merge them as-is.
Decision requested
I'll narrow or close the PRs to match whatever you decide.
Drafted by Claude Opus 5.5 via Claude Code, on behalf of @GuardedAirplane.
All reactions