Fix: notifications broken on Windows (writeFileSync /dev/tty) (#12)

harryalbert · web-flow · commit e5e1a52e0ff5 · 2026-05-29T13:29:11.000-04:00
* fall back to process.stdout.write when writeFileSync fails

* fix package-lock and untrack node_modules/package-lock

* revert some changes
diff --git a/src/notify.ts b/src/notify.ts
@@ -4,16 +4,27 @@ import { writeFileSync } from "fs"
  * Send a Warp notification via OSC 777 escape sequence.
  * Only emits when Warp declares cli-agent protocol support,
  * avoiding garbled output in other terminals (and working over SSH).
+ *
+ * On Unix we write to /dev/tty so the sequence bypasses any
+ * stdout redirection or terminal-multiplexer capture.
+ * On Windows /dev/tty doesn't exist, so we fall back to
+ * process.stdout which works because OpenCode plugins run
+ * in-process (sharing the same ConPTY-connected stdout).
  */
 function warpNotify(title: string, body: string): void {
   if (!process.env.WARP_CLI_AGENT_PROTOCOL_VERSION) return
 
+  const sequence = `\x1b]777;notify;${title};${body}\x07`
+
   try {
-    // OSC 777 format: \033]777;notify;<title>;<body>\007
-    const sequence = `\x1b]777;notify;${title};${body}\x07`
     writeFileSync("/dev/tty", sequence)
   } catch {
-    // Silently ignore if /dev/tty is not available
+    // /dev/tty unavailable (e.g. Windows) — write to stdout instead.
+    try {
+      process.stdout.write(sequence)
+    } catch {
+      // Silently ignore if stdout is also unavailable
+    }
   }
 }
 
