Before submitting
Area
apps/desktop
Steps to reproduce
- Pick an idle thread (no run in progress, provider session
stopped).
- Open the thread actions and choose Snooze.
- Set a custom wake time a few days out.
- Look at the sidebar.
Expected behavior
The thread leaves the active list. It shows only in the Snoozed section until its wake time.
Actual behavior
The thread shows in the Snoozed section with the correct wake time. It also stays in the active list. It never goes away until I settle or archive it.
The server state looks correct. Two threads I snoozed today, read from projection_threads:
|
Thread A |
Thread B |
snoozed_at |
2026-10-06T16:13:07Z |
2026-10-06T16:13:18Z |
snoozed_until |
2026-10-10T17:13:00Z |
2026-10-10T17:13:00Z |
pinned_at / settled_at / archived_at |
null |
null |
| pending approvals / user input / plan |
0 / 0 / 0 |
0 / 0 / 0 |
| session status |
stopped |
stopped |
unsettled_at |
null |
2026-10-04T12:26:30Z |
So snoozed_until is in the future, but the desktop sidebar still renders the thread in the active list.
Impact
Snooze doesn't clear the sidebar, so I can't park threads. I run many threads at once, so the active list stays cluttered.
Version or commit
T3 Code (Alpha) 0.0.45 desktop (Electron 44.4.2), server t3 v0.0.45
Environment
macOS desktop client connected to a remote t3 serve on a Mac mini.
Workaround
None. Settling or archiving the thread hides it, but that is not the same as a timed snooze.
Related
Different from #6368 (snooze lost after work finishes), #15130 (snoozed thread comes back early) and #11788 (snoozed threads vanish).
Before submitting
Area
apps/desktop
Steps to reproduce
stopped).Expected behavior
The thread leaves the active list. It shows only in the Snoozed section until its wake time.
Actual behavior
The thread shows in the Snoozed section with the correct wake time. It also stays in the active list. It never goes away until I settle or archive it.
The server state looks correct. Two threads I snoozed today, read from
projection_threads:snoozed_atsnoozed_untilpinned_at/settled_at/archived_atstoppedstoppedunsettled_atSo
snoozed_untilis in the future, but the desktop sidebar still renders the thread in the active list.Impact
Snooze doesn't clear the sidebar, so I can't park threads. I run many threads at once, so the active list stays cluttered.
Version or commit
T3 Code (Alpha) 0.0.45 desktop (Electron 44.4.2), server
t3 v0.0.45Environment
macOS desktop client connected to a remote
t3 serveon a Mac mini.Workaround
None. Settling or archiving the thread hides it, but that is not the same as a timed snooze.
Related
Different from #6368 (snooze lost after work finishes), #15130 (snoozed thread comes back early) and #11788 (snoozed threads vanish).