Repository navigation
Sidebar: visual divider between pinned and unpinned threads #21908
Replies: 2 comments
|
Related: #22958 proposes making Pinned a collapsible section (expanded by default, with a count and activity dot when collapsed), plus a separate collapsible "Saved" section for long-lived reference threads. A collapsible header would also give the visible boundary this discussion asks for. |
|
Note 🤖 GPT-6.1 Sol responding on behalf of Etan Etan built a compact, Arc-style alternative for making the pinned block distinct, inspired by @thegenioo's X feedback and his generated concept. Pins fit up to three across based on sidebar width, keep T3's native theme and existing status icons, and fill a short final row. Drafts stay above them. Dragging shifts peers live and previews the destination width.
Zero to five pins, then reorder:
Fork draft #23 — source, before/after images, both themes, draft states and full recordings. No upstream PR. This also overlaps with #17319's density request. This is a reviewed prototype: peer labels can briefly cross during reflow, and the bounded performance samples don't establish large-list or exhaustive CPU/GPU performance. Would this compact direction be useful alongside the divider proposed here? 🤖 Generated with Claude Opus 5.5 and GPT-6.1 Sol in T3 Code Nightly |






Uh oh!
There was an error while loading. Please reload this page.
Problem
Pinned threads sit at the top of the sidebar, but nothing marks where they end. The only cue is the small pin icon, which is easy to miss when scanning, so it's hard to tell at a glance where the pinned block stops and the regular threads begin.
My use case: I keep my recurring automations (threads bound to
schedule_task) pinned, because that's the only stable place for them today. The pinned block is effectively my "automations" area, and without a visual boundary it blends into the threads I'm actively working in.Proposal
Render a thin divider after the last pinned thread.
Mockup (the first three threads are pinned):
A nice extra, not required: let the pinned block collapse, the way Working / Snoozed / Settled can.
Smallest useful scope
Just the divider. No new setting needed, unless the maintainers prefer it opt-in.
Related
All reactions