@rainmanhhh/pi-web 0.15.24 → 0.15.26

package/README.md

@@ -48,28 +48,18 @@ Set `PI_WEB_PASSWORD` to protect the web interface and every API endpoint with H
 Pi Web can invoke a high-privilege agent. Basic Auth does not encrypt the password in transit, so do not expose plain HTTP to the internet. Use HTTPS through a trusted reverse proxy or a trusted VPN for remote access.
 API requests accept loopback names, IP literals, and exact comma-separated names in `PI_WEB_ALLOWED_HOSTS`. Configure that variable when a trusted reverse proxy uses a different external hostname. `PI_WEB_HOSTNAME` is a legacy alias for the same allow-list — it does **not** control the bind address (use `HOST` for that).
 
-## HTTP Proxy
+## Runtime: Node.js or Bun
 
-Pi Web reads the standard `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY` environment variables for server-side model and API requests.
+The published bundle declares `#!/usr/bin/env node`, and every launcher honours that shebang — the Windows npm shim calls Node, and Bun spawns a Node process too. So **Node is the default runtime everywhere**.
 
-On macOS or Linux:
+Bun is supported as well and starts faster (its file I/O helps most with projects that have many session files). Bun respects shebangs, so using it is explicit — `--bun` goes **before** the package name:
 
 ```bash
-HTTP_PROXY=http://127.0.0.1:7890 \
-HTTPS_PROXY=http://127.0.0.1:7890 \
-NO_PROXY=localhost,127.0.0.1 \
-npx @rainmanhhh/pi-web@latest
-```
-
-On Windows PowerShell:
-
-```powershell
-$env:HTTP_PROXY = "http://127.0.0.1:7890"
-$env:HTTPS_PROXY = "http://127.0.0.1:7890"
-$env:NO_PROXY = "localhost,127.0.0.1"
-npx @rainmanhhh/pi-web@latest
+bunx --bun @rainmanhhh/pi-web@latest   # run without installing
+bunx --bun pi-web                      # when installed globally
 ```
 
+Plain `bunx pi-web` still runs on Node. Node remains the tested configuration; if something misbehaves under Bun, retry on Node first to tell runtime differences apart from real bugs.
 ## Features
 
 - **Pick work back up**: browse previous pi conversations by project without digging through terminal history or session paths.
@@ -92,6 +82,7 @@ npx @rainmanhhh/pi-web@latest
 - **Git worktrees**: see [Worktrees in Pi Web](./docs/worktrees.md) for when the switcher appears, how new worktrees are created, and what removal does.
 - **Forks vs in-session branches**: Fork creates a new `.jsonl` file. "Edit from here" creates another branch inside the same session file.
 - **Internationalization**: see [Internationalization](./docs/i18n.md) for using translations and adding languages or UI text.
+- **Proxy support**: Pi Web does **not** read `HTTP_PROXY`, `HTTPS_PROXY`, or `NO_PROXY`. To reach upstream model APIs through a proxy, use a system-level tool (TUN / transparent proxy) instead — it needs no application support and covers every request.
 
 ## Development
 
@@ -144,7 +135,7 @@ server/
   routes/       # API handlers: agent, auth, cwd, files, git, models,
                 #   sessions, skills, worktrees, preferences, project-trust, …
   static.ts     # serves dist/static in production (single-process mode)
-  mount.ts      # Next-style route-module adapter for Hono
+  mount.ts      # route-module adapter for Hono (one route.ts per path)
 scripts/        # e2e-stop, cdp-capture helpers
 tests/e2e/      # Playwright specs and fixtures
 vite.config.ts        # dev server (:30001), /api proxy → :30002, build outDir

package/README.zh-CN.md

@@ -46,28 +46,18 @@ PI_WEB_PASSWORD='足够长的随机密码' pi-web  # 启用 Basic Auth（用户
 Pi Web 可以调用高权限智能体。Basic Auth 不会加密传输中的密码，因此不要把明文 HTTP 暴露到互联网。远程访问时应使用可信反向代理提供 HTTPS，或通过可信 VPN 访问。
 API 请求仅接受 loopback 名称、IP 字面量，以及 `PI_WEB_ALLOWED_HOSTS` 中以逗号分隔的精确主机名。可信反向代理使用不同的外部主机名时，请配置该变量。`PI_WEB_HOSTNAME` 是该白名单的旧别名，**不**控制监听地址（绑定地址请用 `HOST`）。
 
-## HTTP 代理
+## 运行时：Node.js 还是 Bun
 
-Pi Web 的服务端模型请求和 API 请求会读取标准的 `HTTP_PROXY`、`HTTPS_PROXY` 和 `NO_PROXY` 环境变量。
+发布产物里声明的是 `#!/usr/bin/env node`，各启动器都会遵循这个 shebang —— Windows 的 npm shim 调用 Node，Bun 也会启动 Node 进程来执行。因此**默认运行时始终是 Node**。
 
-macOS 或 Linux：
+Pi Web 同样支持 Bun，且启动更快（会话文件很多的项目收益最明显）。Bun 默认尊重 shebang，所以要显式指定，`--bun` 必须写在包名**之前**：
 
 ```bash
-HTTP_PROXY=http://127.0.0.1:7890 \
-HTTPS_PROXY=http://127.0.0.1:7890 \
-NO_PROXY=localhost,127.0.0.1 \
-npx @rainmanhhh/pi-web@latest
-```
-
-Windows PowerShell：
-
-```powershell
-$env:HTTP_PROXY = "http://127.0.0.1:7890"
-$env:HTTPS_PROXY = "http://127.0.0.1:7890"
-$env:NO_PROXY = "localhost,127.0.0.1"
-npx @rainmanhhh/pi-web@latest
+bunx --bun @rainmanhhh/pi-web@latest   # 无需安装，直接运行
+bunx --bun pi-web                      # 已全局安装时
 ```
 
+直接 `bunx pi-web` 仍然跑在 Node 上。Node 是经过充分测试的配置；如果在 Bun 下出现异常，请先换回 Node 复现，以区分运行时差异与程序缺陷。
 ## 功能介绍
 
 - **把历史工作接回来**：打开网页就能按项目找到以前的 pi 对话，不必在终端里翻文件或记住会话路径。
@@ -90,6 +80,7 @@ npx @rainmanhhh/pi-web@latest
 - **Git worktree**：什么时候显示切换器、新建目录在哪里、删除会影响什么，见 [Pi Web 里的 Worktree](./docs/worktrees.zh-CN.md)。
 - **Fork 与会话内分支不同**：Fork 会创建新的 `.jsonl` 文件；“Edit from here” 是同一会话文件里的分支。
 - **国际化**：翻译使用与新增语言/UI 文案的方法见 [Internationalization](./docs/i18n.md)。
+- **代理支持**：Pi Web **不会**读取 `HTTP_PROXY`、`HTTPS_PROXY` 和 `NO_PROXY`。需要让服务端请求走代理时，请改用系统层方案（TUN / 透明代理）——无需应用配合，且覆盖所有请求。
 
 ## 开发
 
@@ -142,7 +133,7 @@ server/
   routes/       # API 处理器：agent、auth、cwd、files、git、models、
                 #   sessions、skills、worktrees、preferences、project-trust 等
   static.ts     # 生产环境提供 dist/static（单进程模式）
-  mount.ts      # Next 风格路由模块到 Hono 的适配
+  mount.ts      # 路由模块（每个路径一个 route.ts）到 Hono 的适配
 scripts/        # e2e-stop、cdp-capture 辅助脚本
 tests/e2e/      # Playwright 测试与 fixtures
 vite.config.ts        # dev server（:30001）、/api 代理 → :30002、build outDir