oc-bg-color-sync 0.0.1 → 0.0.2

package/README.md

@@ -44,6 +44,10 @@ This plugin restores the OSC 11 sync as a userland workaround until upstream fin
 - After the native call, converts the RGBA color to hex and writes `OSC 11;rgb:rr/gg/bb\x07` to stdout
 - On plugin dispose, calls `renderer.resetTerminalBgColor()` which writes `OSC 111\x07`
 
+### Timing fix
+
+`ThemeProvider` calls `setBackgroundColor()` during initial render **before** plugins are loaded. If we only patched the method, the terminal would stay out of sync until the theme changed again. The plugin therefore reads `api.theme.current.background` after patching and calls the patched method once to force an immediate sync.
+
 ### OSC sequence reference
 
 - **OSC 11** — Set terminal background color  
@@ -63,6 +67,23 @@ Add the plugin to your OpenCode config (`tui.json` or equivalent):
 }
 ```
 
+## Debugging
+
+To verify the plugin is emitting OSC sequences, run OpenCode in a terminal that logs escape sequences, or sniff stdout with `script`:
+
+```bash
+# Start a typescript session; all escape sequences are recorded
+script -q /tmp/opencode-osc.log
+opencode
+# quit opencode, then exit the script shell
+exit
+# Search for OSC 11/111 in the log
+grep -o $'\x1b]11;[^\x07]*\x07' /tmp/opencode-osc.log
+grep -o $'\x1b]111\x07' /tmp/opencode-osc.log
+```
+
+You should see an `OSC 11` on startup and an `OSC 111` on exit.
+
 ## Requirements
 
 - A terminal emulator that supports OSC 11/111 (most modern terminals do; Ghostty has quirks with theme detection after OSC 11/111 usage)

package/index.ts

@@ -1,5 +1,6 @@
 import type { TuiPlugin, TuiPluginModule } from "@opencode-ai/plugin/tui";
 import { hexToRgb } from "@opentui/core";
+import { writeSync } from "fs";
 
 const tui: TuiPlugin = async (api) => {
   const renderer = api.renderer;
@@ -9,16 +10,36 @@ const tui: TuiPlugin = async (api) => {
     original(color);
     const rgba = typeof color === "string" ? hexToRgb(color) : color;
 
-    if (rgba.a > 0) {
-      const hex = (n: number) => n.toString(16).padStart(2, "0");
-      process.stdout.write(
-        `\x1b]11;rgb:${hex(rgba.r)}/${hex(rgba.g)}/${hex(rgba.b)}\x07`,
-      );
+    if (rgba && rgba.a > 0) {
+      const hex = (n: number) =>
+        Math.round(n * 255)
+          .toString(16)
+          .padStart(2, "0");
+      const seq = `\x1b]11;rgb:${hex(rgba.r)}/${hex(rgba.g)}/${hex(rgba.b)}\x07`;
+      try {
+        writeSync(1, seq);
+      } catch {
+        process.stdout.write(seq);
+      }
     }
   };
 
+  // ThemeProvider calls setBackgroundColor during initial render, which happens
+  // *before* plugins are loaded. After patching we must force a re-sync with the
+  // current theme background so the terminal matches on startup.
+  renderer.setBackgroundColor(api.theme.current.background);
+
   api.lifecycle.onDispose(() => {
-    renderer.resetTerminalBgColor();
+    // Use writeSync(1, …) instead of process.stdout.write so the OSC 111
+    // sequence bypasses Node.js stream buffering and is flushed to the kernel
+    // before the process exits.  renderer.resetTerminalBgColor() uses
+    // process.stdout.write, which can leave bytes in the stream buffer that
+    // never get drained when the event loop shuts down.
+    try {
+      writeSync(1, "\x1b]111\x07");
+    } catch {
+      renderer.resetTerminalBgColor();
+    }
   });
 };
 

package/package.json

@@ -1,8 +1,7 @@
 {
   "name": "oc-bg-color-sync",
-  "version": "0.0.1",
+  "version": "0.0.2",
   "type": "module",
-  "main": "index.ts",
   "exports": {
     "./tui": {
       "import": "./index.ts"