remote-codex 0.11.45 → 0.11.49

package/README.md

@@ -26,9 +26,10 @@ home or office workstation through an inbound port.
 - npm CLI: `npm install -g remote-codex`
 
 Native Windows Relay Supervisor support targets Windows 11 x64 with Node.js 22
-and Codex. The Terminal plugin is not available on Windows. See
-[Native Windows support](docs/windows.md) for setup, background management, and
-the current compatibility boundary.
+and Codex. The self-contained [Windows Device Manager](docs/windows-device-manager.zh.md)
+installs missing runtime components and keeps the device available from the system
+tray. The Terminal plugin is not available on Windows. See
+[Native Windows support](docs/windows.md) for the current compatibility boundary.
 
 ### Why Remote Codex
 
@@ -71,7 +72,8 @@ client to load the latest transcript and continue from the current state.
   approvals or structured questions remotely.
 - Select agent backend, model, reasoning effort, collaboration mode, and
   approval policy when starting work.
-- Work with Codex, Claude, and OpenCode backends through one supervisor surface.
+- Work with Codex, Claude, OpenCode, and any ACP-compatible agent through one
+  supervisor surface.
 - Upload attachments and export transcripts as PDF or HTML.
 
 #### Workspaces and files
@@ -200,8 +202,10 @@ REMOTE_CODEX_RELAY_SUPERVISOR_PORT=45679 \
 remote-codex relay-supervisor
 ```
 
-`45679` is used by default in copied setup commands to avoid common local
-`8787` port conflicts. You can change it if needed.
+Copied setup commands use `45679` for macOS/Linux and `45680` for Windows by
+default. The distinct ports allow a Windows host and WSL to run supervisors at
+the same time, while both avoid common local `8787` port conflicts. You can
+change either port if needed.
 
 By default, `remote-codex relay-supervisor` starts itself inside a detached
 `tmux` session so closing the terminal does not take the device offline. Manage
@@ -235,6 +239,39 @@ use it only on a trusted LAN/VPN. Set `SERVICE_HOST=127.0.0.1` and
 
 Override with `SERVICE_PORT` and `SERVICE_API_PORT`.
 
+### ACP Agents
+
+Enable the generic ACP backend, then choose the concrete agent when creating a
+thread:
+
+```bash
+REMOTE_CODEX_ENABLED_AGENT_PROVIDERS=acp \
+remote-codex start
+```
+
+The supervisor detects the base agent first. Missing base agents remain disabled
+and show their probe command. When a base agent exists but its ACP adapter is
+missing, the create-thread form offers an adapter install action.
+
+| Agent | ACP transport | Base probe | ACP command |
+| --- | --- | --- | --- |
+| Grok Build | Native | `grok --version` | `grok agent stdio` |
+| Cursor Agent | Native | `cursor-agent --version` | `cursor-agent acp` |
+| OpenAI Codex | Adapter | `codex --version` | `codex-acp` |
+| Claude Agent | Adapter | `claude --version` | `claude-agent-acp` |
+| Gemini CLI | Native | `gemini --version` | `gemini --acp` |
+| GitHub Copilot CLI | Native | `copilot --version` | `copilot --acp` |
+| OpenCode | Native | `opencode --version` | `opencode acp` |
+| DeepSeek Harness | Adapter | `dsh --version` | `dsh-acp` |
+
+`ACP_COMMAND` remains available for an additional custom ACP stdio server.
+
+`ACP_STARTUP_TIMEOUT_MS` controls initialize timeout. ACP agents may support
+`session/load`, `session/resume`, both, or neither. Remote Codex persists every
+normalized turn item in its supervisor SQLite database, so transcript history
+remains available even when an ACP agent resumes context without replaying old
+turns.
+
 ### Development
 
 ```bash
@@ -285,8 +322,9 @@ Remote Codex 支持本机、Tailscale/LAN 和公网 Relay 三种访问方式。R
 - npm CLI: `npm install -g remote-codex`
 
 原生 Windows Relay Supervisor 首版支持 Windows 11 x64、Node.js 22 和 Codex；
-Windows 暂不提供 Terminal 插件。安装、后台运行方法和兼容范围见
-[原生 Windows 支持说明](docs/windows.md)。
+自包含的 [Windows Device Manager](docs/windows-device-manager.zh.md) 可以探测并
+补齐运行环境，通过系统托盘维持 Device 在线。Windows 暂不提供 Terminal 插件，
+兼容范围见 [原生 Windows 支持说明](docs/windows.md)。
 
 ### 为什么使用 Remote Codex
 
@@ -325,7 +363,7 @@ flowchart LR
 - 查看流式回答、reasoning 摘要、工具调用、运行状态、token 使用和完成状态。
 - Agent 运行期间继续发送指令，并远程处理授权请求或结构化问题。
 - 创建任务时选择 Agent backend、模型、reasoning effort、协作模式和授权策略。
-- 在同一个 Supervisor 界面使用 Codex、Claude 和 OpenCode backend。
+- 在同一个 Supervisor 界面使用 Codex、Claude、OpenCode 和任意 ACP 兼容 Agent。
 - 上传附件，并将 transcript 导出为 PDF 或 HTML。
 
 #### Workspace 与文件
@@ -447,7 +485,9 @@ REMOTE_CODEX_RELAY_SUPERVISOR_PORT=45679 \
 remote-codex relay-supervisor
 ```
 
-复制命令默认使用 `45679`，用于避开本机常见的 `8787` 端口冲突；需要时可以手动换。
+复制命令默认在 macOS/Linux 使用 `45679`，在 Windows 使用 `45680`。两个端口互不
+相同，因此 Windows 主机和 WSL 可以同时运行 supervisor，并且都能避开本机常见的
+`8787` 端口冲突；需要时可以手动修改。
 
 默认情况下，`remote-codex relay-supervisor` 会尝试启动到 detached `tmux`
 session 里，这样关闭终端窗口不会让设备下线。可以用下面命令管理：
@@ -480,6 +520,36 @@ npm CLI 默认端口：
 
 可用 `SERVICE_PORT` 和 `SERVICE_API_PORT` 覆盖。
 
+### ACP Agent
+
+启用通用 ACP backend，然后在创建 thread 时选择具体 Agent：
+
+```bash
+REMOTE_CODEX_ENABLED_AGENT_PROVIDERS=acp \
+remote-codex start
+```
+
+Supervisor 会先探测基础 Agent。基础 Agent 不存在时选项保持灰色并显示探测命令；
+基础 Agent 已存在但缺少 ACP adapter 时，创建 thread 界面会提供 adapter 安装按钮。
+
+| Agent | ACP 接入方式 | 基础探测 | ACP 命令 |
+| --- | --- | --- | --- |
+| Grok Build | 原生 | `grok --version` | `grok agent stdio` |
+| Cursor Agent | 原生 | `cursor-agent --version` | `cursor-agent acp` |
+| OpenAI Codex | Adapter | `codex --version` | `codex-acp` |
+| Claude Agent | Adapter | `claude --version` | `claude-agent-acp` |
+| Gemini CLI | 原生 | `gemini --version` | `gemini --acp` |
+| GitHub Copilot CLI | 原生 | `copilot --version` | `copilot --acp` |
+| OpenCode | 原生 | `opencode --version` | `opencode acp` |
+| DeepSeek Harness | Adapter | `dsh --version` | `dsh-acp` |
+
+`ACP_COMMAND` 仍可用于额外配置一个自定义 ACP stdio server。
+
+`ACP_STARTUP_TIMEOUT_MS` 用于控制 initialize 超时。ACP Agent 可能支持
+`session/load`、`session/resume`、同时支持两者，或都不支持。Remote Codex 会把
+所有规范化后的 turn item 持久化到 supervisor SQLite，因此即使 Agent 恢复上下文时
+不回放旧 turn，前端 transcript 历史仍然可用。
+
 ### 开发
 
 ```bash

package/apps/relay-server/dist/index.js

@@ -5869,7 +5869,7 @@ function isAllowedSharedRuntimeMetadataRequest(method, pathname) {
   if (pathname === "/api/plugins") {
     return true;
   }
-  return /^\/api\/agent-runtimes\/[^/]+\/(?:status|models|subscription-usage)$/.test(pathname);
+  return /^\/api\/agent-runtimes\/[^/]+\/(?:status|models|agents|subscription-usage)$/.test(pathname);
 }
 function threadIdFromPath(pathValue) {
   const pathname = new URL(pathValue, "http://relay.local").pathname;