pi-web-ui 0.21.2 → 0.22.0

package/README.md

@@ -1,74 +1,84 @@
-# pi-web-ui
-
-**English** | [简体中文](https://github.com/xing-shuyin/pi-web-ui/blob/main/README.zh-CN.md)
-
-A web chat interface for the [pi coding agent](https://pi.dev) — the agent runs
-in-process via the pi SDK and streams events to the browser over WebSocket. Chat
-with thinking blocks and tool calls, attach files, ask about images, use a
-built-in terminal, manage models, and more. Requires Node.js ≥ 22.19 and a
-configured pi install.
-
-## Screenshots
-
-![pi-web-ui main interface](https://cdn.jsdelivr.net/gh/xing-shuyin/pi-web-ui@main/assets/shot.jpeg)
-
-## Install
-
-```bash
-npm i -g pi-web-ui            # global install (recommended)
-npx pi-web-ui                 # or run without installing (latest, starts on :8787)
-npm i -g .                    # or install the local checkout
-```
-
-## Start
-
-```bash
-pi-web-ui                                           # foreground, http://localhost:8787
-PORT=9000 PI_WEB_CWD=/path/to/project pi-web-ui     # custom port / workspace
-```
-
-## Stop
-
-- **Foreground**: press `Ctrl+C` in the terminal running it.
-- **As a service**: `pi-web-ui server stop` (stops the instance; auto-start stays until `server uninstall`).
-
-## Update
-
-```bash
-npm i -g pi-web-ui@latest     # upgrade to the latest published version
-pi-web-ui server restart      # restart the service to apply it (foreground: restart manually)
-```
-
-## Uninstall
-
-```bash
-npm uninstall -g pi-web-ui
-```
-
-Uninstalling does **not** delete your chats — session data lives in
-`<cwd>/.pi-web` (or `PI_WEB_DATA_DIR`) and survives uninstall/upgrade.
-
-## Run as a system service (auto-start on boot)
-
-```bash
-pi-web-ui server install --port 9000 --cwd /path/to/project   # install + start
-pi-web-ui server status                     # running? auto-start?
-pi-web-ui server restart                    # restart (applies config/version changes)
-pi-web-ui server stop                       # stop (auto-start stays)
-pi-web-ui server start                      # start again
-pi-web-ui server uninstall                  # remove the service entirely
-pi-web-ui server shortcut                   # desktop one-click launch icon
-```
-
-- **macOS** → launchd agent (no sudo), logs to `/tmp/pi-web-ui.log` / `.err`
-- **Linux** → systemd unit (`systemctl enable --now`), logs via `journalctl -u pi-web-ui -f`
-- **Windows** → Task Scheduler logon task (hidden PowerShell window, no black console)
-
-Options: `--port` (default 8787), `--cwd` (workspace), `--data-dir` (sessions),
-`--name` (custom service name). Rerunning `server install` with new options
-regenerates the config and restarts the service — that's how you change its
-port/cwd.
-
-## License
-
-MIT
+# pi-web-ui
+
+**English** | [简体中文](https://github.com/xing-shuyin/pi-web-ui/blob/main/README.zh-CN.md)
+
+A web chat interface for the [pi coding agent](https://pi.dev) — the agent runs
+in-process via the pi SDK and streams events to the browser over WebSocket. Chat
+with thinking blocks and tool calls, attach files, ask about images, use a
+built-in terminal, manage models, tweak the system prompt, toggle skills and
+extensions on/off, and save/apply settings presets — all from a settings panel.
+Requires Node.js ≥ 22.19 and a configured pi install.
+
+## Screenshots
+
+![pi-web-ui main interface](https://cdn.jsdelivr.net/gh/xing-shuyin/pi-web-ui@main/assets/shot.jpeg)
+
+## Install
+
+```bash
+npm i -g pi-web-ui            # global install (recommended)
+npx pi-web-ui                 # or run without installing (latest, starts on :8787)
+npm i -g .                    # or install the local checkout
+```
+
+**npm ≥ 12?** npm 12+ blocks dependency install scripts by default (you'll see
+`npm warn install-scripts … blocked`). node-pty is a native module, so allow its
+script (the other two packages it lists are harmless no-ops — allowing them just
+silences the warning):
+
+```bash
+npm i -g --allow-scripts=node-pty,@google/genai,protobufjs pi-web-ui@latest
+```
+
+## Start
+
+```bash
+pi-web-ui                                           # foreground, http://localhost:8787
+PORT=9000 PI_WEB_CWD=/path/to/project pi-web-ui     # custom port / workspace
+```
+
+## Stop
+
+- **Foreground**: press `Ctrl+C` in the terminal running it.
+- **As a service**: `pi-web-ui server stop` (stops the instance; auto-start stays until `server uninstall`).
+
+## Update
+
+```bash
+npm i -g pi-web-ui@latest     # upgrade to the latest published version
+pi-web-ui server restart      # restart the service to apply it (foreground: restart manually)
+```
+
+## Uninstall
+
+```bash
+npm uninstall -g pi-web-ui
+```
+
+Uninstalling does **not** delete your chats — session data lives in
+`<cwd>/.pi-web` (or `PI_WEB_DATA_DIR`) and survives uninstall/upgrade.
+
+## Run as a system service (auto-start on boot)
+
+```bash
+pi-web-ui server install --port 9000 --cwd /path/to/project   # install + start
+pi-web-ui server status                     # running? auto-start?
+pi-web-ui server restart                    # restart (applies config/version changes)
+pi-web-ui server stop                       # stop (auto-start stays)
+pi-web-ui server start                      # start again
+pi-web-ui server uninstall                  # remove the service entirely
+pi-web-ui server shortcut                   # desktop one-click launch icon
+```
+
+- **macOS** → launchd agent (no sudo), logs to `/tmp/pi-web-ui.log` / `.err`
+- **Linux** → systemd unit (`systemctl enable --now`), logs via `journalctl -u pi-web-ui -f`
+- **Windows** → Task Scheduler logon task (hidden PowerShell window, no black console)
+
+Options: `--port` (default 8787), `--cwd` (workspace), `--data-dir` (sessions),
+`--name` (custom service name). Rerunning `server install` with new options
+regenerates the config and restarts the service — that's how you change its
+port/cwd.
+
+## License
+
+MIT

package/README.zh-CN.md

@@ -1,71 +1,79 @@
-# pi-web-ui
-
-[English](https://github.com/xing-shuyin/pi-web-ui/blob/main/README.md) | **简体中文**
-
-[pi 编码智能体](https://pi.dev) 的 Web 聊天界面 —— 智能体通过 pi SDK 在服务端进程内运行，
-事件经 WebSocket 流式推送到浏览器。支持思考块与工具调用、附件与图片问答、内置终端、
-模型管理等功能。需要 Node.js ≥ 22.19 及配置好的 pi 环境。
-
-## 界面截图
-
-![pi-web-ui 主界面](https://cdn.jsdelivr.net/gh/xing-shuyin/pi-web-ui@main/assets/shot.jpeg)
-
-## 安装
-
-```bash
-npm i -g pi-web-ui            # 全局安装（推荐）
-npx pi-web-ui                 # 或免安装直接跑（拉取最新版，启动在 :8787）
-npm i -g .                    # 或安装本地 checkout
-```
-
-## 启动
-
-```bash
-pi-web-ui                                           # 前台，http://localhost:8787
-PORT=9000 PI_WEB_CWD=/path/to/project pi-web-ui     # 自定义端口 / 工作目录
-```
-
-## 停止
-
-- **前台**：在运行它的终端里按 `Ctrl+C`。
-- **作为服务**：`pi-web-ui server stop`（停止实例；开机自启保留，直到 `server uninstall`）。
-
-## 更新
-
-```bash
-npm i -g pi-web-ui@latest     # 升级到最新发布版本
-pi-web-ui server restart      # 重启服务使新版本生效（前台运行则手动重启）
-```
-
-## 卸载
-
-```bash
-npm uninstall -g pi-web-ui
-```
-
-卸载**不会**删除你的聊天记录 —— 会话数据存放在 `<cwd>/.pi-web`（或 `PI_WEB_DATA_DIR`），
-卸载/升级后依然保留。
-
-## 作为系统服务（开机自启）
-
-```bash
-pi-web-ui server install --port 9000 --cwd /path/to/project   # 安装 + 启动
-pi-web-ui server status                     # 运行中？开机自启？
-pi-web-ui server restart                    # 重启（应用配置/版本变更）
-pi-web-ui server stop                       # 停止（开机自启保留）
-pi-web-ui server start                      # 再次启动
-pi-web-ui server uninstall                  # 彻底移除服务
-pi-web-ui server shortcut                   # 桌面一键启动图标
-```
-
-- **macOS** → launchd 代理（无需 sudo），日志 `/tmp/pi-web-ui.log` / `.err`
-- **Linux** → systemd unit（`systemctl enable --now`），日志 `journalctl -u pi-web-ui -f`
-- **Windows** → 计划任务（登录自启，隐藏 PowerShell 窗口，无黑窗）
-
-选项：`--port`（默认 8787）、`--cwd`（工作目录）、`--data-dir`（会话目录）、
-`--name`（自定义服务名）。重复执行 `server install` 并传入新选项即可重新生成配置
-并重启服务 —— 这就是修改已装服务端口/工作目录的方式。
-
-## License
-
-MIT
+# pi-web-ui
+
+[English](https://github.com/xing-shuyin/pi-web-ui/blob/main/README.md) | **简体中文**
+
+[pi 编码智能体](https://pi.dev) 的 Web 聊天界面 —— 智能体通过 pi SDK 在服务端进程内运行，
+事件经 WebSocket 流式推送到浏览器。支持思考块与工具调用、附件与图片问答、内置终端、
+模型管理，以及设置面板（自定义系统提示词、技能/插件开关、设置预设一键应用）等功能。
+需要 Node.js ≥ 22.19 及配置好的 pi 环境。
+
+## 界面截图
+
+![pi-web-ui 主界面](https://cdn.jsdelivr.net/gh/xing-shuyin/pi-web-ui@main/assets/shot.jpeg)
+
+## 安装
+
+```bash
+npm i -g pi-web-ui            # 全局安装（推荐）
+npx pi-web-ui                 # 或免安装直接跑（拉取最新版，启动在 :8787）
+npm i -g .                    # 或安装本地 checkout
+```
+
+**npm ≥ 12？** npm 12+ 默认阻止依赖安装脚本（会看到 `npm warn install-scripts … blocked` 警告）。
+node-pty 是原生模块，需要放行其脚本（其余两个包只是 no-op/纯提示，一并放行可消除警告）：
+
+```bash
+npm i -g --allow-scripts=node-pty,@google/genai,protobufjs pi-web-ui@latest
+```
+
+## 启动
+
+```bash
+pi-web-ui                                           # 前台，http://localhost:8787
+PORT=9000 PI_WEB_CWD=/path/to/project pi-web-ui     # 自定义端口 / 工作目录
+```
+
+## 停止
+
+- **前台**：在运行它的终端里按 `Ctrl+C`。
+- **作为服务**：`pi-web-ui server stop`（停止实例；开机自启保留，直到 `server uninstall`）。
+
+## 更新
+
+```bash
+npm i -g pi-web-ui@latest     # 升级到最新发布版本
+pi-web-ui server restart      # 重启服务使新版本生效（前台运行则手动重启）
+```
+
+## 卸载
+
+```bash
+npm uninstall -g pi-web-ui
+```
+
+卸载**不会**删除你的聊天记录 —— 会话数据存放在 `<cwd>/.pi-web`（或 `PI_WEB_DATA_DIR`），
+卸载/升级后依然保留。
+
+## 作为系统服务（开机自启）
+
+```bash
+pi-web-ui server install --port 9000 --cwd /path/to/project   # 安装 + 启动
+pi-web-ui server status                     # 运行中？开机自启？
+pi-web-ui server restart                    # 重启（应用配置/版本变更）
+pi-web-ui server stop                       # 停止（开机自启保留）
+pi-web-ui server start                      # 再次启动
+pi-web-ui server uninstall                  # 彻底移除服务
+pi-web-ui server shortcut                   # 桌面一键启动图标
+```
+
+- **macOS** → launchd 代理（无需 sudo），日志 `/tmp/pi-web-ui.log` / `.err`
+- **Linux** → systemd unit（`systemctl enable --now`），日志 `journalctl -u pi-web-ui -f`
+- **Windows** → 计划任务（登录自启，隐藏 PowerShell 窗口，无黑窗）
+
+选项：`--port`（默认 8787）、`--cwd`（工作目录）、`--data-dir`（会话目录）、
+`--name`（自定义服务名）。重复执行 `server install` 并传入新选项即可重新生成配置
+并重启服务 —— 这就是修改已装服务端口/工作目录的方式。
+
+## License
+
+MIT

package/dist/server/agent-service.js

@@ -334,6 +334,25 @@ function killPidTree(pid) {
         // already dead
     }
 }
+/** Best-effort process name for a pid (tasklist on win32, ps on POSIX).
+ *  Returns undefined when the process is gone or the lookup fails. */
+async function lookupProcessName(pid) {
+    try {
+        const { execFile } = await import("node:child_process");
+        if (process.platform === "win32") {
+            const out = await new Promise((resolve, reject) => execFile("tasklist", ["/FI", `PID eq ${pid}`, "/FO", "CSV", "/NH"], { windowsHide: true, timeout: 4000 }, (err, stdout) => (err ? reject(err) : resolve(stdout))));
+            // CSV: "node.exe","12345",...
+            const m = out.match(/"([^"]+)"/);
+            return m ? m[1] : undefined;
+        }
+        const out = await new Promise((resolve, reject) => execFile("ps", ["-o", "comm=", "-p", String(pid)], { timeout: 4000 }, (err, stdout) => (err ? reject(err) : resolve(stdout))));
+        const name = out.trim();
+        return name || undefined;
+    }
+    catch {
+        return undefined;
+    }
+}
 /**
  * Cheap per-message discriminator for the serialization cache key. Persisted
  * message content never changes, so this is stable across snapshots, while
@@ -1001,8 +1020,15 @@ export class ClientSession {
      *  end-of-execution diff reveals servers the agent left running in the
      *  background (e.g. `npm run dev &`). Keyed by port → pid. */
     bashListenBefore = null;
-    /** Background servers the agent started (port → pid). 「中断」kills them. */
+    /** Background servers the agent started (port → pid). Managed from the
+     *  后台任务 panel: each can be stopped individually or all at once. The
+     *  map lives on the CLIENT (not a conversation), so it survives
+     *  conversation switches/ends and only empties when a task is stopped or
+     *  its process exits on its own (pruned by refreshBgServers). */
     bgServers = new Map();
+    /** Periodic pruner: re-snapshots listening ports and drops tracked entries
+     *  whose process died on its own, keeping the panel honest. */
+    bgTimer = null;
     /** The active conversation (all session operations target it). */
     get conv() {
         const conv = this.convs.get(this.activeId);
@@ -1052,6 +1078,10 @@ export class ClientSession {
         this.stateStore = stateStore;
         this.settings = stateStore.getSettings(clientId);
         this.presets = stateStore.getPresets(clientId);
+        // Prune dead background tasks every 30s (only spawns netstat/lsof while
+        // the list is non-empty). unref: must not keep the process alive.
+        this.bgTimer = setInterval(() => void this.refreshBgServers(), 30_000);
+        this.bgTimer.unref?.();
     }
     static async create(clientId, cwd, stateStore) {
         const agentDir = process.env.PI_CODING_AGENT_DIR ?? getAgentDir();
@@ -1204,6 +1234,9 @@ export class ClientSession {
         // Reconnect: push the settings panel state (prompt text/mode, skill &
         // extension toggles, saved presets).
         this.pushSettings();
+        // Reconnect: push the background-task list — it must survive reconnects
+        // and outlive the conversation that started the tasks.
+        this.emitBgServers();
     }
     detachSink(send) {
         this.sinks.delete(send);
@@ -2998,17 +3031,9 @@ export class ClientSession {
      * overnight. The notice fires only on the forced-reset path.
      */
     async abort() {
+        // 只停止智能体运行本身；AI 在后台启动的服务由「后台任务」面板单独
+        // 管理（可逐个停止或全部关闭），不会在停止对话时被连带杀掉。
         await this.interruptRun(this.conv, "已停止");
-        // 中断同时清理 AI 在后台启动的服务（npm run dev & 等）——避免用户
-        // 测试时发现端口被占用而不知道是什么进程。
-        const killed = await this.killBackgroundServers();
-        if (killed.length > 0) {
-            this.emit({
-                type: "notice",
-                level: "info",
-                text: `已停止 AI 后台服务：端口 ${killed.join("、")}（进程已结束）`,
-            });
-        }
         this.flushSnapshot();
     }
     /** After a bash tool run, wait briefly for background servers to bind,
@@ -3021,19 +3046,92 @@ export class ClientSession {
             return;
         await new Promise((r) => setTimeout(r, 1500));
         const after = await snapshotListeningPorts();
+        let added = false;
         for (const [port, pid] of after) {
             if (!before.has(port) && !this.bgServers.has(port)) {
                 this.bgServers.set(port, { pid, since: Date.now() });
+                added = true;
+                // Best-effort process name so the panel shows something readable.
+                void lookupProcessName(pid).then((name) => {
+                    const cur = this.bgServers.get(port);
+                    if (cur && cur.pid === pid && name) {
+                        cur.name = name;
+                        this.emitBgServers();
+                    }
+                });
                 this.emit({
                     type: "notice",
                     level: "info",
-                    text: `检测到 AI 启动的后台服务：端口 ${port}（pid ${pid}）——点顶栏「中断」可停止`,
+                    text: `检测到 AI 启动的后台服务：端口 ${port}（pid ${pid}）——可在顶栏「后台任务」里单独停止或全部关闭`,
                 });
             }
         }
+        if (added)
+            this.emitBgServers();
+    }
+    /** The current background-server list, oldest first. */
+    bgServerList() {
+        return [...this.bgServers.entries()]
+            .map(([port, v]) => ({
+            port,
+            pid: v.pid,
+            since: v.since,
+            ...(v.name ? { name: v.name } : {}),
+        }))
+            .sort((a, b) => a.since - b.since);
+    }
+    /** Push the current background-task list to every connected socket. */
+    emitBgServers() {
+        this.emit({ type: "bg_servers", servers: this.bgServerList() });
+    }
+    /** Re-snapshot listening ports and drop tracked entries that are no longer
+     *  listening — the process exited on its own, so it must leave the panel.
+     *  Port AND pid must both match: a port reused by an unrelated process is
+     *  not our server anymore. Silent (the list just updates). */
+    async refreshBgServers() {
+        if (this.disposed || this.bgServers.size === 0)
+            return;
+        const now = await snapshotListeningPorts();
+        let changed = false;
+        for (const [port, v] of [...this.bgServers]) {
+            if (now.get(port) !== v.pid) {
+                this.bgServers.delete(port);
+                changed = true;
+            }
+        }
+        if (changed)
+            this.emitBgServers();
+    }
+    /** Re-push the current list on request (panel opened); prunes dead entries first. */
+    async listBgServers() {
+        await this.refreshBgServers();
+        this.emitBgServers();
+    }
+    /** Kill ONE background server (by port); returns whether anything was killed. */
+    async killBackgroundServer(port) {
+        const entry = this.bgServers.get(port);
+        if (!entry) {
+            this.emit({
+                type: "notice",
+                level: "info",
+                text: `端口 ${port} 不在后台任务列表中`,
+            });
+            this.flushSnapshot();
+            return false;
+        }
+        killPidTree(entry.pid);
+        this.bgServers.delete(port);
+        this.emitBgServers();
+        this.emit({
+            type: "notice",
+            level: "info",
+            text: `已停止后台任务：端口 ${port}（pid ${entry.pid}）`,
+        });
+        this.flushSnapshot();
+        return true;
     }
     /** Kill every background server the agent started; returns the freed ports. */
-    async killBackgroundServers() {
+    async killAllBackgroundServers() {
         if (this.bgServers.size === 0)
             return [];
         const killed = [];
@@ -3042,6 +3140,7 @@ export class ClientSession {
             killed.push(String(port));
         }
         this.bgServers.clear();
+        this.emitBgServers();
         return killed;
     }
     /** Kill only the running bash command(s) — the agent run itself continues
@@ -4608,6 +4707,10 @@ export class ClientSession {
         }
         this.unwatchDir();
         this.webUi.dispose();
+        if (this.bgTimer) {
+            clearInterval(this.bgTimer);
+            this.bgTimer = null;
+        }
         for (const conv of this.convs.values()) {
             this.clearAllToolWatchdogs(conv);
             conv.unsubscribe?.();

package/dist/server/index.js

@@ -240,6 +240,15 @@ wss.on("connection", (ws) => {
             case "abort_bash":
                 void cs.abortBash();
                 break;
+            case "kill_background_server":
+                void cs.killBackgroundServer(msg.port);
+                break;
+            case "kill_background_servers":
+                void cs.killAllBackgroundServers();
+                break;
+            case "list_bg_servers":
+                void cs.listBgServers();
+                break;
             case "new_chat":
                 void cs.newChat();
                 break;

package/dist/server/patch-node-pty.js

@@ -0,0 +1,80 @@
+/**
+ * node-pty × Node `--watch` compatibility patches (dev-server noise).
+ *
+ * Node's `--watch` mode (the dev script runs `node --watch --import tsx`)
+ * pushes `watch:require` / `watch:import` messages over the IPC channels of
+ * spawned worker threads AND forked child processes to track module
+ * dependencies. node-pty 1.1.0 does not recognize these and mishandles them in
+ * two places:
+ *
+ *  · windowsConoutConnection.js — logs every unknown worker message via
+ *    `console.warn`, producing hundreds of "Unexpected ConoutWorkerMessage"
+ *    lines per terminal (the SCM panel's hidden query PTY triggers it on every
+ *    git-view open).
+ *  · windowsPtyAgent.js — the kill path's `_getConsoleProcessList()` treats ANY
+ *    message from the forked console-list agent as its reply; a watch message
+ *    has no `consoleProcessList` property, so `message.consoleProcessList` is
+ *    undefined and the `.forEach` on it crashes the server.
+ *
+ * Both are benign protocol noise: the ConPTY worker only ever sends its READY
+ * sentinel and the agent only sends `{ consoleProcessList }` — both of which
+ * node-pty handles. These patches make node-pty ignore unrelated IPC traffic.
+ *
+ * IMPORTANT: this module MUST be imported before node-pty (see terminals.ts) —
+ * it rewrites the installed copies on disk so the subsequently-compiled
+ * node-pty modules contain the fixed handlers. Best-effort and idempotent
+ * (checks before rewriting), mirroring the spawn-helper chmod self-heal; a
+ * read-only node_modules or a different node-pty version just skips the patch
+ * (the runtime console.warn filter in terminals.ts still guards the flood).
+ */
+import { existsSync, readFileSync, writeFileSync } from "node:fs";
+import { createRequire } from "node:module";
+import { dirname, join } from "node:path";
+const require = createRequire(import.meta.url);
+/** Absolute path of the installed node-pty package root, or null. */
+function ptyPackageDir() {
+    try {
+        // require.resolve("node-pty") → <pkg>/lib/index.js → package root is two up.
+        return dirname(dirname(require.resolve("node-pty")));
+    }
+    catch {
+        return null;
+    }
+}
+/** Idempotently replace one code fragment in a node-pty source file. */
+function patchFile(pkgDir, rel, find, replace) {
+    try {
+        const file = join(pkgDir, rel);
+        if (!existsSync(file))
+            return;
+        const src = readFileSync(file, "utf8");
+        if (src.includes(replace))
+            return; // already patched
+        if (!src.includes(find))
+            return; // unexpected content — leave alone
+        writeFileSync(file, src.replace(find, replace), "utf8");
+    }
+    catch {
+        // best-effort — the runtime console.warn filter still guards the flood
+    }
+}
+function applyPatches() {
+    const pkgDir = ptyPackageDir();
+    if (!pkgDir)
+        return;
+    // 1. ConoutConnection: ignore unknown worker messages instead of warning.
+    patchFile(pkgDir, "lib/windowsConoutConnection.js", "console.warn('Unexpected ConoutWorkerMessage', message);", "break; // pi-web-ui: ignore Node --watch worker messages");
+    // 2. windowsPtyAgent kill path: only accept a real console-list reply
+    //    (watch messages arrive first on the fork channel and carry no
+    //    consoleProcessList — previously resolved undefined and crashed).
+    patchFile(pkgDir, "lib/windowsPtyAgent.js", "agent.on('message', function (message) {\n                clearTimeout(timeout);\n                resolve(message.consoleProcessList);\n            });", [
+        "            agent.on('message', function (message) {",
+        "                // pi-web-ui: ignore Node --watch messages on the fork channel",
+        "                if (message && Array.isArray(message.consoleProcessList)) {",
+        "                    clearTimeout(timeout);",
+        "                    resolve(message.consoleProcessList);",
+        "                }",
+        "            });",
+    ].join("\n"));
+}
+applyPatches();

package/dist/server/terminals.js

@@ -18,6 +18,10 @@ import { mkdir, readFile, writeFile } from "node:fs/promises";
 import { createRequire } from "node:module";
 import { homedir } from "node:os";
 import { dirname, isAbsolute, join, resolve } from "node:path";
+// MUST run before node-pty is required: rewrites the installed node-pty copies
+// so their worker/agent handlers tolerate Node `--watch`'s IPC traffic (see the
+// module itself for details).
+import "./patch-node-pty.js";
 import { spawn } from "node-pty";
 /** Location of the command list for a project: <workspaceRoot>/.pi/commands.json */
 export function commandsFilePath(workspaceRoot) {
@@ -164,6 +168,25 @@ function shellEnv() {
     return env;
 }
 // ---------------------------------------------------------------------------
+// node-pty ConoutConnection warning noise (Node --watch)
+// ---------------------------------------------------------------------------
+// node-pty's ConoutConnection warns about every unknown message from its ConPTY
+// worker thread. Under `node --watch` (the dev server: `node --watch --import
+// tsx`), Node's watch mode pushes `watch:require` / `watch:import` messages over
+// the worker's message channel to track module dependencies; node-pty doesn't
+// recognize them and logs one `Unexpected ConoutWorkerMessage { … }` per message
+// — hundreds of lines per terminal (the SCM panel's hidden query PTY triggers it
+// on every git-view open). The messages are harmless: the worker only ever sends
+// its READY sentinel, which the handler does process. Filter that exact warning
+// at the console boundary so dev output stays readable. Production runs without
+// --watch and never produces these.
+const originalWarn = console.warn.bind(console);
+console.warn = (...args) => {
+    if (args[0] === "Unexpected ConoutWorkerMessage")
+        return;
+    originalWarn(...args);
+};
+// ---------------------------------------------------------------------------
 // spawn-helper permission repair (node-pty macOS prebuilds)
 // ---------------------------------------------------------------------------
 // node-pty 1.1.0 publishes its macOS prebuilds with `spawn-helper` lacking the