pi-web-ui 0.15.5 → 0.16.0

package/deploy/com.xingshuyin.pi-web-ui.plist

@@ -1,48 +1,48 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
-<!--
-  pi-web-ui launchd agent — macOS auto-start at login.
-
-  Install:
-    npm i -g pi-web-ui
-    cp deploy/com.xingshuyin.pi-web-ui.plist ~/Library/LaunchAgents/
-    # edit ProgramArguments / WorkingDirectory / PI_WEB_CWD for your setup
-    launchctl load ~/Library/LaunchAgents/com.xingshuyin.pi-web-ui.plist
-    # (or: launchctl bootstrap gui/$(id -u) ~/Library/LaunchAgents/com.xingshuyin.pi-web-ui.plist)
-
-  Find the pi-web-ui binary path with: which pi-web-ui
--->
-<plist version="1.0">
-<dict>
-  <key>Label</key>
-  <string>com.xingshuyin.pi-web-ui</string>
-
-  <key>ProgramArguments</key>
-  <array>
-    <string>/usr/local/bin/pi-web-ui</string>
-  </array>
-
-  <key>RunAtLoad</key>
-  <true/>
-
-  <!-- Restart if it crashes -->
-  <key>KeepAlive</key>
-  <true/>
-
-  <key>WorkingDirectory</key>
-  <string>/Users/YOUR_USER</string>
-
-  <key>EnvironmentVariables</key>
-  <dict>
-    <key>PORT</key>
-    <string>8787</string>
-    <key>PI_WEB_CWD</key>
-    <string>/Users/YOUR_USER</string>
-  </dict>
-
-  <key>StandardOutPath</key>
-  <string>/tmp/pi-web-ui.log</string>
-  <key>StandardErrorPath</key>
-  <string>/tmp/pi-web-ui.err</string>
-</dict>
-</plist>
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<!--
+  pi-web-ui launchd agent — macOS auto-start at login.
+
+  Install:
+    npm i -g pi-web-ui
+    cp deploy/com.xingshuyin.pi-web-ui.plist ~/Library/LaunchAgents/
+    # edit ProgramArguments / WorkingDirectory / PI_WEB_CWD for your setup
+    launchctl load ~/Library/LaunchAgents/com.xingshuyin.pi-web-ui.plist
+    # (or: launchctl bootstrap gui/$(id -u) ~/Library/LaunchAgents/com.xingshuyin.pi-web-ui.plist)
+
+  Find the pi-web-ui binary path with: which pi-web-ui
+-->
+<plist version="1.0">
+<dict>
+  <key>Label</key>
+  <string>com.xingshuyin.pi-web-ui</string>
+
+  <key>ProgramArguments</key>
+  <array>
+    <string>/usr/local/bin/pi-web-ui</string>
+  </array>
+
+  <key>RunAtLoad</key>
+  <true/>
+
+  <!-- Restart if it crashes -->
+  <key>KeepAlive</key>
+  <true/>
+
+  <key>WorkingDirectory</key>
+  <string>/Users/YOUR_USER</string>
+
+  <key>EnvironmentVariables</key>
+  <dict>
+    <key>PORT</key>
+    <string>8787</string>
+    <key>PI_WEB_CWD</key>
+    <string>/Users/YOUR_USER</string>
+  </dict>
+
+  <key>StandardOutPath</key>
+  <string>/tmp/pi-web-ui.log</string>
+  <key>StandardErrorPath</key>
+  <string>/tmp/pi-web-ui.err</string>
+</dict>
+</plist>

package/deploy/nginx-subpath.conf

@@ -1,78 +1,78 @@
-# pi-web-ui behind nginx at a sub-path: http://<host>:83/pi/
-# Backend app: http://127.0.0.1:8787  (default PORT env)
-#
-# Topology:
-#   LAN users     → http://192.168.1.101:83/pi/   (plain HTTP listener)
-#   frp (public)  → 39.99.235.208:60018 → 127.0.0.1:83 (PROXY protocol v2)
-#
-# frpc sends PROXY v2 to nginx (transport.proxyProtocolVersion = "v2"), so
-# direct LAN connections MUST NOT require it — two listeners, one port:
-#   * 127.0.0.1:83        proxy_protocol — only the local frp client connects
-#     here (it speaks PROXY v2; nginx then sees the real visitor IP).
-#   * 192.168.1.101:83    plain HTTP — LAN browsers, no PROXY header needed.
-#
-# The frontend uses absolute paths (/ws WebSocket, /assets/*, /favicon.svg,
-# /api/file…) so those get their own proxied locations next to /pi/.
-
-# Reuse for Upgrade/Connection headers (WebSocket).
-map $http_upgrade $connection_upgrade {
-    default upgrade;
-    ''      close;
-}
-
-server {
-    listen 127.0.0.1:83 proxy_protocol;
-    listen 192.168.1.101:83;
-
-    server_name _;
-
-    # Trust PROXY-protocol headers only from the local frp client; plain
-    # (LAN) connections keep their real $remote_addr untouched.
-    set_real_ip_from 127.0.0.1;
-    real_ip_header proxy_protocol;
-
-    # ---- main entry: strip /pi/ and forward to the app root ----
-    location /pi/ {
-        proxy_pass http://127.0.0.1:8787/;
-        proxy_http_version 1.1;
-        proxy_set_header Host $host;
-        proxy_set_header X-Real-IP $remote_addr;
-        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
-        proxy_set_header X-Forwarded-Proto $scheme;
-        proxy_set_header Upgrade $http_upgrade;
-        proxy_set_header Connection $connection_upgrade;
-    }
-
-    # ---- WebSocket (the frontend connects to ws://<host>/ws) ----
-    location /ws {
-        proxy_pass http://127.0.0.1:8787;
-        proxy_http_version 1.1;
-        proxy_set_header Upgrade $http_upgrade;
-        proxy_set_header Connection $connection_upgrade;
-        proxy_read_timeout 3600s;
-        proxy_send_timeout 3600s;
-        proxy_set_header X-Real-IP $remote_addr;
-        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
-    }
-
-    # ---- absolute asset paths baked into index.html ----
-    location /assets/ {
-        proxy_pass http://127.0.0.1:8787;
-    }
-    location = /favicon.svg {
-        proxy_pass http://127.0.0.1:8787;
-    }
-    location = /favicon-streaming.svg {
-        proxy_pass http://127.0.0.1:8787;
-    }
-
-    # ---- media preview / download / health API ----
-    location /api/ {
-        proxy_pass http://127.0.0.1:8787;
-    }
-
-    # bare root → app entry
-    location = / {
-        return 302 /pi/;
-    }
-}
+# pi-web-ui behind nginx at a sub-path: http://<host>:83/pi/
+# Backend app: http://127.0.0.1:8787  (default PORT env)
+#
+# Topology:
+#   LAN users     → http://192.168.1.101:83/pi/   (plain HTTP listener)
+#   frp (public)  → 39.99.235.208:60018 → 127.0.0.1:83 (PROXY protocol v2)
+#
+# frpc sends PROXY v2 to nginx (transport.proxyProtocolVersion = "v2"), so
+# direct LAN connections MUST NOT require it — two listeners, one port:
+#   * 127.0.0.1:83        proxy_protocol — only the local frp client connects
+#     here (it speaks PROXY v2; nginx then sees the real visitor IP).
+#   * 192.168.1.101:83    plain HTTP — LAN browsers, no PROXY header needed.
+#
+# The frontend uses absolute paths (/ws WebSocket, /assets/*, /favicon.svg,
+# /api/file…) so those get their own proxied locations next to /pi/.
+
+# Reuse for Upgrade/Connection headers (WebSocket).
+map $http_upgrade $connection_upgrade {
+    default upgrade;
+    ''      close;
+}
+
+server {
+    listen 127.0.0.1:83 proxy_protocol;
+    listen 192.168.1.101:83;
+
+    server_name _;
+
+    # Trust PROXY-protocol headers only from the local frp client; plain
+    # (LAN) connections keep their real $remote_addr untouched.
+    set_real_ip_from 127.0.0.1;
+    real_ip_header proxy_protocol;
+
+    # ---- main entry: strip /pi/ and forward to the app root ----
+    location /pi/ {
+        proxy_pass http://127.0.0.1:8787/;
+        proxy_http_version 1.1;
+        proxy_set_header Host $host;
+        proxy_set_header X-Real-IP $remote_addr;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header X-Forwarded-Proto $scheme;
+        proxy_set_header Upgrade $http_upgrade;
+        proxy_set_header Connection $connection_upgrade;
+    }
+
+    # ---- WebSocket (the frontend connects to ws://<host>/ws) ----
+    location /ws {
+        proxy_pass http://127.0.0.1:8787;
+        proxy_http_version 1.1;
+        proxy_set_header Upgrade $http_upgrade;
+        proxy_set_header Connection $connection_upgrade;
+        proxy_read_timeout 3600s;
+        proxy_send_timeout 3600s;
+        proxy_set_header X-Real-IP $remote_addr;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+    }
+
+    # ---- absolute asset paths baked into index.html ----
+    location /assets/ {
+        proxy_pass http://127.0.0.1:8787;
+    }
+    location = /favicon.svg {
+        proxy_pass http://127.0.0.1:8787;
+    }
+    location = /favicon-streaming.svg {
+        proxy_pass http://127.0.0.1:8787;
+    }
+
+    # ---- media preview / download / health API ----
+    location /api/ {
+        proxy_pass http://127.0.0.1:8787;
+    }
+
+    # bare root → app entry
+    location = / {
+        return 302 /pi/;
+    }
+}

package/deploy/pi-web-ui-task.xml

@@ -1,71 +1,71 @@
-<?xml version="1.0" encoding="UTF-16"?>
-<!--
-  pi-web-ui Task Scheduler task — Windows auto-start at logon.
-
-  The easy way (no admin needed, generates everything for you):
-    npm i -g pi-web-ui
-    pi-web-ui server install --port 8787 --cwd C:\path\to\project
-    pi-web-ui server status | restart | stop | uninstall
-
-  Manual install with this template (edit the paths below first):
-    schtasks /Create /TN "pi-web-ui" /XML pi-web-ui-task.xml /F
-    schtasks /Run /TN "pi-web-ui"
-
-  Notes:
-    - The task runs the PowerShell launcher the CLI generates at
-      %APPDATA%\pi-web-ui\pi-web-ui.ps1 with -WindowStyle Hidden, so the
-      server runs with no black console window (nothing to accidentally
-      close/kill). The ps1 sets PORT/PI_WEB_CWD, cd's to the workspace,
-      launches node, and appends output to %USERPROFILE%\pi-web-ui.log.
-      Preview both generated files with: pi-web-ui server install --print
-    - Save this file as UTF-16 LE (schtasks requires it; the CLI does this
-      automatically when it writes the task XML).
-    - LogonTrigger = starts when you log in, same as a launchd user agent.
-      For boot-start without login, use Docker instead (see README).
--->
-<Task version="1.2" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
-  <RegistrationInfo>
-    <Description>pi-web-ui — web chat for the pi coding agent (auto-start at logon)</Description>
-  </RegistrationInfo>
-  <Triggers>
-    <LogonTrigger>
-      <Enabled>true</Enabled>
-    </LogonTrigger>
-  </Triggers>
-  <Principals>
-    <Principal id="Author">
-      <LogonType>InteractiveToken</LogonType>
-      <RunLevel>LeastPrivilege</RunLevel>
-    </Principal>
-  </Principals>
-  <Settings>
-    <MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
-    <DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>
-    <StopIfGoingOnBatteries>false</StopIfGoingOnBatteries>
-    <AllowHardTerminate>true</AllowHardTerminate>
-    <StartWhenAvailable>false</StartWhenAvailable>
-    <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
-    <IdleSettings>
-      <StopOnIdleEnd>false</StopOnIdleEnd>
-      <RestartOnIdle>false</RestartOnIdle>
-    </IdleSettings>
-    <AllowStartOnDemand>true</AllowStartOnDemand>
-    <Enabled>true</Enabled>
-    <Hidden>false</Hidden>
-    <RunOnlyIfIdle>false</RunOnlyIfIdle>
-    <WakeToRun>false</WakeToRun>
-    <ExecutionTimeLimit>PT0S</ExecutionTimeLimit>
-    <Priority>7</Priority>
-    <RestartOnFailure>
-      <Interval>PT1M</Interval>
-      <Count>3</Count>
-    </RestartOnFailure>
-  </Settings>
-  <Actions Context="Author">
-    <Exec>
-      <Command>C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe</Command>
-      <Arguments>-NoProfile -NonInteractive -ExecutionPolicy Bypass -WindowStyle Hidden -File "%APPDATA%\pi-web-ui\pi-web-ui.ps1"</Arguments>
-      <WorkingDirectory>%USERPROFILE%</WorkingDirectory>
-    </Exec>
-  </Actions>
-</Task>
+<?xml version="1.0" encoding="UTF-16"?>
+<!--
+  pi-web-ui Task Scheduler task — Windows auto-start at logon.
+
+  The easy way (no admin needed, generates everything for you):
+    npm i -g pi-web-ui
+    pi-web-ui server install --port 8787 --cwd C:\path\to\project
+    pi-web-ui server status | restart | stop | uninstall
+
+  Manual install with this template (edit the paths below first):
+    schtasks /Create /TN "pi-web-ui" /XML pi-web-ui-task.xml /F
+    schtasks /Run /TN "pi-web-ui"
+
+  Notes:
+    - The task runs the PowerShell launcher the CLI generates at
+      %APPDATA%\pi-web-ui\pi-web-ui.ps1 with -WindowStyle Hidden, so the
+      server runs with no black console window (nothing to accidentally
+      close/kill). The ps1 sets PORT/PI_WEB_CWD, cd's to the workspace,
+      launches node, and appends output to %USERPROFILE%\pi-web-ui.log.
+      Preview both generated files with: pi-web-ui server install --print
+    - Save this file as UTF-16 LE (schtasks requires it; the CLI does this
+      automatically when it writes the task XML).
+    - LogonTrigger = starts when you log in, same as a launchd user agent.
+      For boot-start without login, use Docker instead (see README).
+-->
+<Task version="1.2" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
+  <RegistrationInfo>
+    <Description>pi-web-ui — web chat for the pi coding agent (auto-start at logon)</Description>
+  </RegistrationInfo>
+  <Triggers>
+    <LogonTrigger>
+      <Enabled>true</Enabled>
+    </LogonTrigger>
+  </Triggers>
+  <Principals>
+    <Principal id="Author">
+      <LogonType>InteractiveToken</LogonType>
+      <RunLevel>LeastPrivilege</RunLevel>
+    </Principal>
+  </Principals>
+  <Settings>
+    <MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
+    <DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>
+    <StopIfGoingOnBatteries>false</StopIfGoingOnBatteries>
+    <AllowHardTerminate>true</AllowHardTerminate>
+    <StartWhenAvailable>false</StartWhenAvailable>
+    <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
+    <IdleSettings>
+      <StopOnIdleEnd>false</StopOnIdleEnd>
+      <RestartOnIdle>false</RestartOnIdle>
+    </IdleSettings>
+    <AllowStartOnDemand>true</AllowStartOnDemand>
+    <Enabled>true</Enabled>
+    <Hidden>false</Hidden>
+    <RunOnlyIfIdle>false</RunOnlyIfIdle>
+    <WakeToRun>false</WakeToRun>
+    <ExecutionTimeLimit>PT0S</ExecutionTimeLimit>
+    <Priority>7</Priority>
+    <RestartOnFailure>
+      <Interval>PT1M</Interval>
+      <Count>3</Count>
+    </RestartOnFailure>
+  </Settings>
+  <Actions Context="Author">
+    <Exec>
+      <Command>C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe</Command>
+      <Arguments>-NoProfile -NonInteractive -ExecutionPolicy Bypass -WindowStyle Hidden -File "%APPDATA%\pi-web-ui\pi-web-ui.ps1"</Arguments>
+      <WorkingDirectory>%USERPROFILE%</WorkingDirectory>
+    </Exec>
+  </Actions>
+</Task>

package/deploy/pi-web-ui.service

@@ -1,31 +1,31 @@
-# pi-web-ui systemd unit — Linux auto-start on boot.
-#
-# Install (adjust User/WorkingDirectory/Environment to taste):
-#   sudo npm i -g pi-web-ui
-#   sudo cp deploy/pi-web-ui.service /etc/systemd/system/
-#   sudo systemctl daemon-reload
-#   sudo systemctl enable --now pi-web-ui
-#   sudo systemctl status pi-web-ui
-#
-# Logs: journalctl -u pi-web-ui -f
-
-[Unit]
-Description=pi-web-ui — web chat for the pi coding agent
-After=network.target
-
-[Service]
-Type=simple
-# Run as an unprivileged user (change to your user, e.g. yourname)
-User=YOUR_USER
-# The workspace the agent operates in (read/edit/bash/write)
-WorkingDirectory=/home/YOUR_USER
-Environment=PORT=8787
-# Point at your pi config dir if it's not the default ~/.pi/agent
-#Environment=PI_CODING_AGENT_DIR=/home/YOUR_USER/.pi/agent
-ExecStart=/usr/bin/pi-web-ui
-Restart=on-failure
-RestartSec=5
-# npm global bin may live elsewhere (nvm, etc.) — find with: which pi-web-ui
-
-[Install]
-WantedBy=multi-user.target
+# pi-web-ui systemd unit — Linux auto-start on boot.
+#
+# Install (adjust User/WorkingDirectory/Environment to taste):
+#   sudo npm i -g pi-web-ui
+#   sudo cp deploy/pi-web-ui.service /etc/systemd/system/
+#   sudo systemctl daemon-reload
+#   sudo systemctl enable --now pi-web-ui
+#   sudo systemctl status pi-web-ui
+#
+# Logs: journalctl -u pi-web-ui -f
+
+[Unit]
+Description=pi-web-ui — web chat for the pi coding agent
+After=network.target
+
+[Service]
+Type=simple
+# Run as an unprivileged user (change to your user, e.g. yourname)
+User=YOUR_USER
+# The workspace the agent operates in (read/edit/bash/write)
+WorkingDirectory=/home/YOUR_USER
+Environment=PORT=8787
+# Point at your pi config dir if it's not the default ~/.pi/agent
+#Environment=PI_CODING_AGENT_DIR=/home/YOUR_USER/.pi/agent
+ExecStart=/usr/bin/pi-web-ui
+Restart=on-failure
+RestartSec=5
+# npm global bin may live elsewhere (nvm, etc.) — find with: which pi-web-ui
+
+[Install]
+WantedBy=multi-user.target

package/dist/server/agent-service.js

@@ -11,7 +11,7 @@
  * so reconnects just re-request a snapshot.
  */
 import { spawn } from "node:child_process";
-import { existsSync, readFileSync, statSync, writeFileSync, mkdirSync, } from "node:fs";
+import { existsSync, readFileSync, statSync, writeFileSync, mkdirSync, watch, } from "node:fs";
 import { dirname, join, relative, resolve, sep } from "node:path";
 import { fileURLToPath } from "node:url";
 import { createAgentSessionFromServices, createAgentSessionRuntime, createAgentSessionServices, getAgentDir, SessionManager, } from "@earendil-works/pi-coding-agent";
@@ -728,6 +728,14 @@ export class ClientSession {
     disposed = false;
     /** pi-config readiness check, cached briefly so 60ms snapshots don't hit disk. */
     piCheckCache = null;
+    /** fs.watch on the currently-listed directory — file changes push an instant
+     *  refresh (`file_changed`) so the tree updates without waiting for the 10s
+     *  poll. Only the listed directory is watched (one level); navigating
+     *  re-watches the new target. fs.watch isn't available on every platform /
+     *  filesystem — failures silently fall back to the poll. */
+    fsWatcher = null;
+    watchPath = null;
+    watchTimer = null;
     constructor(clientId, cwd, agentDir, stateStore) {
         this.clientId = clientId;
         this.cwd = cwd;
@@ -829,8 +837,11 @@ export class ClientSession {
         this.sinks.delete(send);
         // No sockets left for this client — kill its terminals so processes don't
         // survive a closed tab / dropped connection.
-        if (this.sinks.size === 0)
+        if (this.sinks.size === 0) {
             this.terminals.killAll();
+            // No sockets → nobody to refresh; drop the dir watcher too.
+            this.unwatchDir();
+        }
     }
     /** Broadcast to every connected socket of this client. */
     emit(msg) {
@@ -1653,8 +1664,13 @@ export class ClientSession {
                 await s.sendCustomMessage(aside.message, { deliverAs: "nextTurn" });
             }
             if (s.isStreaming) {
-                // Queue for delivery after the current run finishes.
-                await s.prompt(text, { streamingBehavior: "followUp" });
+                // Steer: interrupts the current run — the message is delivered right
+                // after the current assistant turn settles (remaining planned tool
+                // calls are skipped) and the agent immediately responds to it. This
+                // is the pi CLI Enter-during-streaming semantic (docs/usage: Enter
+                // queues a steering message); followUp would wait for the whole run
+                // to finish, which users perceive as ordinary queueing.
+                await s.prompt(text, { streamingBehavior: "steer" });
             }
             else {
                 await s.prompt(text);
@@ -2427,6 +2443,9 @@ export class ClientSession {
             // always use "/", but relative() returns "\\" on Windows.
             const rel = rawRel.split(sep).join("/");
             const { entries, truncated, error } = await readDirForUI(target, rel);
+            // Watch the listed directory (only after a successful read — a missing
+            // dir throws above and must not create a watcher on a phantom path).
+            this.watchDir(target, rel);
             if (error) {
                 // Windows-only: unreadable system dirs degrade to an empty list
                 // with a warning instead of a hard error — the panel stays usable.
@@ -2456,6 +2475,56 @@ export class ClientSession {
             });
         }
     }
+    /** Watch a directory for changes so the file panel refreshes instantly
+     *  instead of waiting for the 10s poll. Watches the directory exactly as
+     *  listed (one level); navigating re-watches the new target. fs.watch is
+     *  unavailable on some platforms/filesystems — failures silently fall back
+     *  to the poll. */
+    watchDir(absPath, rel) {
+        if (this.disposed || this.watchPath === rel)
+            return;
+        this.unwatchDir();
+        this.watchPath = rel;
+        try {
+            // persistent: false — the watcher must not keep the process alive.
+            this.fsWatcher = watch(absPath, { persistent: false }, () => {
+                // Burst events (npm install, git ops, editor save→rename) are
+                // debounced into a single refresh.
+                if (this.watchTimer)
+                    return;
+                this.watchTimer = setTimeout(() => {
+                    this.watchTimer = null;
+                    this.emit({ type: "file_changed", path: this.watchPath ?? "" });
+                }, 400);
+            });
+            this.fsWatcher.on("error", () => {
+                // Directory deleted / unsupported fs — stop watching; the poll (or
+                // the next navigation) restores things.
+                this.unwatchDir();
+            });
+        }
+        catch {
+            // fs.watch unsupported (some network mounts, containers) — poll covers it.
+            this.fsWatcher = null;
+            this.watchPath = null;
+        }
+    }
+    unwatchDir() {
+        if (this.watchTimer) {
+            clearTimeout(this.watchTimer);
+            this.watchTimer = null;
+        }
+        if (this.fsWatcher) {
+            try {
+                this.fsWatcher.close();
+            }
+            catch {
+                // already closed
+            }
+            this.fsWatcher = null;
+        }
+        this.watchPath = null;
+    }
     /** Read a workspace file for the preview panel (size-capped, binary-safe). */
     async readFile(relPath) {
         try {
@@ -2822,6 +2891,7 @@ export class ClientSession {
             clearInterval(this.widgetsTimer);
             this.widgetsTimer = null;
         }
+        this.unwatchDir();
         this.webUi.dispose();
         for (const conv of this.convs.values()) {
             conv.unsubscribe?.();