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
[Bug]: Windows "Thread completed" notifications break through Do Not Disturb #27060
I searched existing issues and did not find a duplicate.
I included enough detail to reproduce or investigate the problem.
Area
apps/web
Steps to reproduce
On Windows 11, turn on Do Not Disturb (the Notifications panel says "You'll only see banners for priority notifications and alarms").
In T3 Code Desktop with desktop notifications enabled, start a thread and switch to another app.
Let the thread finish.
Expected behavior
Do Not Disturb hides the "Thread completed" notification, the same way it hides notifications from other apps.
Actual behavior
The "Thread completed" toast pops up anyway, with a Close button. Other apps' notifications stay hidden, and so do T3 Code's own attention alerts (approval, input, failed, usage limit), because those don't set the flag below.
Cause: since #22520, ThreadNotificationCoordinator creates completion notifications with requireInteraction on Windows:
// Windows drops clicks after a toast moves into Notification Center.requireInteraction: kind==="completion"&&isWindowsPlatform(navigator.platform),
As #22520 says, Electron then sends the toast as a Windows reminder. Windows Do Not Disturb lets reminders through by default, under Settings > System > Notifications > Set priority notifications > "Show reminders regardless of app used". So every completion notification breaks through DND.
The only workaround today is to turn that setting off, which also stops real reminders from other apps (calendar, Outlook) from getting through DND. The other option is to turn off T3 Code's notifications entirely.
fix(web): keep Windows thread notifications clickable until handled #22520: added requireInteraction so that clicks still open the thread after the toast leaves the screen. A fix for this issue probably needs a different way to keep clicks from Notification Center working, so that completion notifications can go back to being normal toasts.
Activity
juliusmarminge commentedon Oct 30, 2026
Closing as a duplicate of #26341, which tracks the same problem. Please follow along there.