Uh oh!
There was an error while loading. Please reload this page.
Fix: notifications broken on Windows (writeFileSync /dev/tty) - #12
Conversation
harryalbert
commented
Apr 16, 2026
2c3c68a to
98cb4e9Comparearijitcodes
commented
May 29, 2026
Any update on when this will be merged and released? |
harryalbert
commented
May 29, 2026
Hey @arijitcodes thanks for pinging! I don't love the approach in this PR so was holding off on merging, and it fell off my radar after that. I think I'll close this PR for now, but if you have a solution for WSL in mind, please feel free to submit a PR and tag me as a reviewer! I'm happy to TAL. It seems like there's a possible solution described in this issue. I also don't have a WSL machine to test on, so if you do end up submitting a fix, could you please attatch a video of the fix WAI? Thank you! |
arijitcodes
commented
May 29, 2026
Hey @harryalbert , Thanks for taking the time to respond. After doing some AI Research, trial and error, i got it working by replacing And after a nice OC restart, it started working - Both as Windows Toast Notification, as well as the Warp In-app notification tray (along with tab icons etc). NOTE: This didnt solve the #18 Notification Badge thing, but atleast got my notifications working. |
harryalbert
commented
May 29, 2026
ah got it, that makes sense. Thanks for clarifying! so would the fix in this PR have solved you issue? |
harryalbert
commented
May 29, 2026
nice, this makes sense! I think I'll probably merge this PR then, because it seems like it might address your issue |
Yes, would appreciate a merge and release tbh lol Also, thanks a ton for your super fast response, appreciate it a ton 🔥 🙌🏻 |
harryalbert
commented
May 29, 2026
of course! Happy to help — thanks for re-raising this! |
Uh oh!
There was an error while loading. Please reload this page.
arijitcodes
commented
May 29, 2026
Ayyyy merged it already, nice. Hope we get a new release soon 😼 |
harryalbert
commented
May 29, 2026
Just published the new version! |






warpNotifywrites the OSC 777 escape sequence viawriteFileSync("/dev/tty", ...)./dev/ttyis a Unix-only device — it doesn't exist on native Windows (PowerShell, CMD). Thecatchblock silently swallows the error, so no notifications ever reach Warp on Windows. This also means the setup chip never disappears, since Warp never receives asession_startevent.The fix is to fall back to
process.stdout.writewhen the first write attempt fails. This matches the pattern used by OpenCode's own clipboard PR and theopencode-terminal-bell-notifiercommunity pluginShould fix#11 (I reached out to folks in the issue thread to ask them to confirm)