pi-web-ui 0.44.2 → 0.45.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,88 +1,88 @@
-# pi-web-ui behind nginx at a sub-path: http://<host>:83/pi/
-# Backend app: http://127.0.0.1:8787  (default PORT env)
-#
-# IMPORTANT: pi-web-ui 0.23+ checks the WebSocket Origin against the request
-# Host (hostname AND port). Every proxied location MUST forward the original
-# Host with $http_host (keeps the port). Using $host (drops the port) or
-# leaving Host unset (defaults to 127.0.0.1:8787) makes the upgrade fail with
-# 403 — the page loads but chat/terminal keep reconnecting.
-#
-# Topology (two listeners on one port: frp + LAN coexist):
-#   frp (public)  -> <PUBLIC_IP>:<PUBLIC_PORT> -> 127.0.0.1:83 (PROXY protocol v2)
-#   LAN users     -> http://<LAN_IP>:83/pi/      (plain HTTP listener)
-#
-# frpc sends PROXY v2 to nginx (transport.proxyProtocolVersion = "v2"):
-#   * 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).
-#   * <LAN_IP>:83    plain HTTP — LAN browsers, no PROXY header needed.
-#
-# Simpler alternative (no real client IPs): drop proxy_protocol entirely and
-# use a single `listen 83;` — then frpc must NOT set proxyProtocolVersion.
-#
-# 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 <LAN_IP>: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;
-        # $http_host keeps the port — origin check compares hostname AND port.
-        proxy_set_header Host $http_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 Host $http_host;
-        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)
+#
+# IMPORTANT: pi-web-ui 0.23+ checks the WebSocket Origin against the request
+# Host (hostname AND port). Every proxied location MUST forward the original
+# Host with $http_host (keeps the port). Using $host (drops the port) or
+# leaving Host unset (defaults to 127.0.0.1:8787) makes the upgrade fail with
+# 403 — the page loads but chat/terminal keep reconnecting.
+#
+# Topology (two listeners on one port: frp + LAN coexist):
+#   frp (public)  -> <PUBLIC_IP>:<PUBLIC_PORT> -> 127.0.0.1:83 (PROXY protocol v2)
+#   LAN users     -> http://<LAN_IP>:83/pi/      (plain HTTP listener)
+#
+# frpc sends PROXY v2 to nginx (transport.proxyProtocolVersion = "v2"):
+#   * 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).
+#   * <LAN_IP>:83    plain HTTP — LAN browsers, no PROXY header needed.
+#
+# Simpler alternative (no real client IPs): drop proxy_protocol entirely and
+# use a single `listen 83;` — then frpc must NOT set proxyProtocolVersion.
+#
+# 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 <LAN_IP>: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;
+        # $http_host keeps the port — origin check compares hostname AND port.
+        proxy_set_header Host $http_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 Host $http_host;
+        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

@@ -10,7 +10,7 @@
  * snapshots. The frontend is snapshot-driven (server is the source of truth),
  * so reconnects just re-request a snapshot.
  */
-import { spawn } from "node:child_process";
+import { spawn, spawnSync } from "node:child_process";
 import { existsSync, readFileSync, rmSync, statSync, writeFileSync, mkdirSync, watch, } from "node:fs";
 import { basename, dirname, join, relative, resolve, sep } from "node:path";
 import { fileURLToPath } from "node:url";
@@ -80,14 +80,14 @@ export class QuiesceRejectedError extends Error {
  *  programs wait for input that never comes. Legacy Chinese files are often
  *  GBK/GB2312 — read them with the right encoding, never paste mojibake into
  *  reasoning/answers. */
-const WINDOWS_PERSONA = `You are a coding agent running on Windows. The bash tool runs Git Bash (bash.exe), not PowerShell. Follow these rules to avoid hanging the session:
-
-
-
-- ALWAYS pass a timeout parameter to the bash tool (in seconds). There is NO default timeout — a command that never finishes (servers, watchers, infinite loops, slow downloads/installs) will hang the entire conversation indefinitely. Pick a generous timeout for long-running work, but never omit it.
-- NEVER run interactive or foreground long-running commands through the bash tool (vi, less, top, python -, node -, npm run dev, sleep 10000). For servers/daemons use background execution with output redirected to a log file, then poll the log; stop them when done.
-- In the interactive terminal (TTY) — which is Git Bash too, not PowerShell — NEVER use heredocs (<<'EOF' ... EOF) or here-strings, and NEVER start interactive programs (vi, less, python -, node -, npm init): they wait for keyboard input that never arrives and hang the terminal forever. Prefer writing a temp script file (e.g. .pi-tmp.sh) and running it non-interactively. ALWAYS pass a timeout to long-running commands (e.g. \`timeout 120 npm run dev\`).
-
+const WINDOWS_PERSONA = `You are a coding agent running on Windows. The bash tool runs Git Bash (bash.exe), not PowerShell. Follow these rules to avoid hanging the session:
+
+
+
+- ALWAYS pass a timeout parameter to the bash tool (in seconds). There is NO default timeout — a command that never finishes (servers, watchers, infinite loops, slow downloads/installs) will hang the entire conversation indefinitely. Pick a generous timeout for long-running work, but never omit it.
+- NEVER run interactive or foreground long-running commands through the bash tool (vi, less, top, python -, node -, npm run dev, sleep 10000). For servers/daemons use background execution with output redirected to a log file, then poll the log; stop them when done.
+- In the interactive terminal (TTY) — which is Git Bash too, not PowerShell — NEVER use heredocs (<<'EOF' ... EOF) or here-strings, and NEVER start interactive programs (vi, less, python -, node -, npm init): they wait for keyboard input that never arrives and hang the terminal forever. Prefer writing a temp script file (e.g. .pi-tmp.sh) and running it non-interactively. ALWAYS pass a timeout to long-running commands (e.g. \`timeout 120 npm run dev\`).
+
 Many legacy Chinese text files (.html/.txt/.md/.log, exported documents) are GBK/GB2312 encoded: the read tool decodes UTF-8 only and will show mojibake (乱码) for them. If a file's content looks garbled, read it through the terminal instead: in Git Bash use \`cat file | iconv -f GBK -t UTF-8\` (or \`iconv -f GBK -t UTF-8 file\`); in cmd use \`chcp 65001 && type file\`; in PowerShell use \`Get-Content -Encoding Default file\`. Never paste mojibake into your reasoning or answer — describe the decoded content instead.`;
 /**
  * Killable bash tool: wraps the SDK bash tool with operations that register
@@ -550,6 +550,8 @@ export class ClientSession {
             flushSnapshot: () => this.flushSnapshot(),
             isDisposed: () => this.disposed,
             getSession: () => this.session,
+            cwd: () => this.cwd,
+            agentDir: () => this.agentDir,
             isStreaming: () => this.session.isStreaming,
             reloadSession: async () => {
                 await this.session.reload();
@@ -1251,6 +1253,7 @@ export class ClientSession {
             tools: state.tools.map((t) => t.name),
             version: ++this.version,
             piConfigured: this.isPiConfigured(),
+            piAgentInstalled: this.isPiCliInstalled(),
             stats,
         };
     }
@@ -1336,6 +1339,38 @@ export class ClientSession {
         this.piCheckCache = { at: now, configured };
         return configured;
     }
+    /**
+     * Whether the pi CLI binary is installed and runnable (`pi --version`
+     * probe). Cached machine-wide (same binary for every client) for 10s —
+     * the check is only rerun after install or when the cache expires.
+     */
+    static piCliProbe = null;
+    static PI_CLI_PROBE_TTL_MS = 10_000;
+    isPiCliInstalled() {
+        const now = Date.now();
+        const cached = ClientSession.piCliProbe;
+        if (cached && now - cached.at < ClientSession.PI_CLI_PROBE_TTL_MS)
+            return cached.installed;
+        let installed = false;
+        try {
+            const res = spawnSync("pi", ["--version"], {
+                timeout: 5000,
+                stdio: "ignore",
+                // Windows: `pi` resolves to a pi.cmd shim — spawnSync can only
+                // exec those through a shell (else ENOENT).
+                shell: process.platform === "win32",
+            });
+            installed = !res.error && res.status === 0;
+        }
+        catch {
+            installed = false;
+        }
+        ClientSession.piCliProbe = { at: now, installed };
+        return installed;
+    }
+    static invalidatePiCliProbe() {
+        ClientSession.piCliProbe = null;
+    }
     /**
      * Run a command async, collecting stdout+stderr; kills on timeout.
      * Never throws / never crashes the server: spawn errors (ENOENT etc.)
@@ -1483,6 +1518,9 @@ export class ClientSession {
                 text: `pi agent 安装失败：${err.message}`,
             });
         }
+        // The CLI may just have landed on PATH (or the install may have failed) —
+        // drop the probe cache so the next snapshot re-checks.
+        ClientSession.invalidatePiCliProbe();
         this.flushSnapshot();
     }
     /** Send a snapshot immediately (cancels any pending throttled one).

package/dist/server/attachments.js

@@ -448,9 +448,9 @@ export async function buildAttachmentMessages(ctx, attachments) {
                         content: [
                             {
                                 type: "text",
-                                text: `
-<vision-bridge>
-${transcript}
+                                text: `
+<vision-bridge>
+${transcript}
 </vision-bridge>`,
                             },
                             ...(pathImg

package/dist/server/client-state.js

@@ -178,6 +178,7 @@ export class ClientStateStore {
             terminalBash: s?.settings?.terminalBash ?? false,
             terminalBashIdleMs: s?.settings?.terminalBashIdleMs ?? 15_000,
             thinkingWrap: s?.settings?.thinkingWrap ?? false,
+            toolsWrap: s?.settings?.toolsWrap ?? true,
             visionBridgeEnabled: s?.settings?.visionBridgeEnabled ?? true,
             visionBridgeModel: s?.settings?.visionBridgeModel ?? null,
             visionBridgePromptMode: s?.settings?.visionBridgePromptMode === "replace" ? "replace" : "append",
@@ -201,6 +202,7 @@ export class ClientStateStore {
             terminalBash: settings.terminalBash ?? cur.terminalBash ?? false,
             terminalBashIdleMs: settings.terminalBashIdleMs ?? cur.terminalBashIdleMs ?? 15_000,
             thinkingWrap: settings.thinkingWrap ?? cur.thinkingWrap ?? false,
+            toolsWrap: settings.toolsWrap ?? cur.toolsWrap ?? true,
             visionBridgeEnabled: settings.visionBridgeEnabled ?? cur.visionBridgeEnabled ?? true,
             visionBridgeModel: settings.visionBridgeModel ?? cur.visionBridgeModel ?? null,
             visionBridgePromptMode: settings.visionBridgePromptMode ??

package/dist/server/index.js

@@ -179,6 +179,11 @@ const here = dirname(fileURLToPath(import.meta.url)); // <pkg>/dist/server or <p
 // Resolve the package root robustly: dev runs from <repo>/server (tsx), prod
 // from <pkg>/dist/server — the ancestor that actually has package.json wins.
 function resolvePkgRoot() {
+    // PI_WEB_PKG_ROOT: Electron 桌面版打包后，server 子进程从 extraResources 目录
+    //（process.resourcesPath）加载 web/dist 和 themes。通过这个 env var 告诉
+    // server 去哪里找 pkgRoot，避免 resolvePkgRoot 的候选路径找不到 package.json。
+    if (process.env.PI_WEB_PKG_ROOT)
+        return process.env.PI_WEB_PKG_ROOT;
     const candidates = [
         resolve(here, ".."),
         resolve(here, "..", ".."),
@@ -717,6 +722,7 @@ wss.on("connection", (ws) => {
                     terminalBash: msg.terminalBash,
                     terminalBashIdleMs: msg.terminalBashIdleMs,
                     thinkingWrap: msg.thinkingWrap,
+                    toolsWrap: msg.toolsWrap,
                     visionBridgeEnabled: msg.visionBridgeEnabled,
                     visionBridgeModel: msg.visionBridgeModel,
                     visionBridgePromptMode: msg.visionBridgePromptMode,

package/dist/server/protocol-version.js

@@ -8,4 +8,4 @@
  * its own copy in web/src/protocol-version.ts; scripts/check-protocol-sync.mjs
  * verifies the two never drift.
  */
-export const PROTOCOL_VERSION = 9;
+export const PROTOCOL_VERSION = 10;