Fix: notifications broken on Windows (writeFileSync /dev/tty)#12
Open
harryalbert wants to merge 2 commits intomainfrom
Open
Fix: notifications broken on Windows (writeFileSync /dev/tty)#12harryalbert wants to merge 2 commits intomainfrom
harryalbert wants to merge 2 commits intomainfrom
Conversation
zachbai
approved these changes
Apr 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

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)