You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Auto-settled threads are hard to find: sort them by when they left the sidebar, and show why they settled
#39115
Threads that auto-settle are hard to find again. I keep a handful of "get to it eventually" threads in the sidebar. When they hit the inactivity timeout they auto-settled, and the only way I found them was paging back through the Settled list to roughly a week earlier and recognising titles.
Three things combine to make this painful:
They land at the wrong place in Settled. The shelf is ordered by settledAt, and auto-settle sets settledAt to the thread's last activity, not to when it actually left the sidebar. A thread that auto-settles today after 7 idle days sorts below everything I settled by hand during that week.
You can't tell manual from automatic. Neither the UI nor t3_thread_list records whether a settle was manual, inactivity, or a merged PR. So you can't ask for "threads that were auto-settled" either. The best proxy I found is a large gap between updatedAt and settledAt, and that's noisy.
If you didn't know auto-settle was on, or don't remember the exact titles, the threads effectively vanish.
What I found in the source
resolveAutoSettlementAt in apps/server/src/orchestration-v2/ThreadSettlementService.ts returns the thread's activity time, both for the inactivity rule and for a merged PR, and that becomes settledAt. sortSettledThreads in packages/client-runtime/src/state/threadSort.ts then orders the shelf by it.
This was deliberate. #9254 stopped recording the time of the periodic auto-settle check as settledAt, because after a restart every old thread looked newly settled. That was a real problem, and any change here should keep it fixed.
What I'm asking for
Order auto-settled threads by when they left the sidebar. For inactivity, last activity + timeout is the moment the thread became eligible. That puts it where you'd expect, and it doesn't flood the top of the shelf after a restart the way the check time did. For a merged PR, the merge time works the same way.
Record and show why a thread settled (manual, inactivity, PR merged). Show it on the settled row and expose it in t3_thread_list, so agents can answer "what got auto-settled?".
Make auto-settles visible when they happen. A small, dismissible line in the Settled section at the bottom of the sidebar, such as "3 threads auto-settled", tinted (yellow or similar) so the change stands out. Clicking it shows those threads. It stays until you dismiss it, so it's still there if you weren't looking when the settle happened. The provider update pill (SidebarProviderUpdatePill) already sets the pattern: the same bg-warning/12 text-warning tone, an X to dismiss, at the bottom of the sidebar.
Light
Dark
(1) alone would have fixed my case. (2) and (3) make it discoverable for anyone who forgot auto-settle was on.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
The problem
Threads that auto-settle are hard to find again. I keep a handful of "get to it eventually" threads in the sidebar. When they hit the inactivity timeout they auto-settled, and the only way I found them was paging back through the Settled list to roughly a week earlier and recognising titles.
Three things combine to make this painful:
settledAt, and auto-settle setssettledAtto the thread's last activity, not to when it actually left the sidebar. A thread that auto-settles today after 7 idle days sorts below everything I settled by hand during that week.t3_thread_listrecords whether a settle was manual, inactivity, or a merged PR. So you can't ask for "threads that were auto-settled" either. The best proxy I found is a large gap betweenupdatedAtandsettledAt, and that's noisy.If you didn't know auto-settle was on, or don't remember the exact titles, the threads effectively vanish.
What I found in the source
resolveAutoSettlementAtinapps/server/src/orchestration-v2/ThreadSettlementService.tsreturns the thread's activity time, both for the inactivity rule and for a merged PR, and that becomessettledAt.sortSettledThreadsinpackages/client-runtime/src/state/threadSort.tsthen orders the shelf by it.This was deliberate. #9254 stopped recording the time of the periodic auto-settle check as
settledAt, because after a restart every old thread looked newly settled. That was a real problem, and any change here should keep it fixed.What I'm asking for
Order auto-settled threads by when they left the sidebar. For inactivity,
last activity + timeoutis the moment the thread became eligible. That puts it where you'd expect, and it doesn't flood the top of the shelf after a restart the way the check time did. For a merged PR, the merge time works the same way.Record and show why a thread settled (manual, inactivity, PR merged). Show it on the settled row and expose it in
t3_thread_list, so agents can answer "what got auto-settled?".Make auto-settles visible when they happen. A small, dismissible line in the Settled section at the bottom of the sidebar, such as "3 threads auto-settled", tinted (yellow or similar) so the change stands out. Clicking it shows those threads. It stays until you dismiss it, so it's still there if you weren't looking when the settle happened. The provider update pill (
SidebarProviderUpdatePill) already sets the pattern: the samebg-warning/12 text-warningtone, an X to dismiss, at the bottom of the sidebar.(1) alone would have fixed my case. (2) and (3) make it discoverable for anyone who forgot auto-settle was on.
Related
settledAtis backdated)🤖 Claude Opus 5.5
All reactions