farming-code 2.2.28 → 2.2.30

package/README.md

@@ -25,19 +25,16 @@ Farming Code runs on the same development machine as your repositories and codin
 
 ## Quick Start
 
-With Node.js 22.13 LTS (22.x) or Node.js 24+ and at least one supported coding CLI installed and signed in:
+With Node.js 22.13 LTS (22.x) or Node.js 24+ and access to a supported coding
+Agent provider:
 
 ```bash
 npm install --global farming-code@latest && farming daemon
 ```
 
-Open one of the authenticated URLs printed by the command, choose **New Agent**, then select a CLI, workspace, and Chat or Terminal. Closing the browser does not stop the Agent. In the same browser, revisit that address; on the development machine, this command prints the local address again:
-
-```bash
-farming url
-```
-
-For a new remote browser, use the authenticated **Network** URL printed when `farming daemon` starts. A VPN, SSH tunnel, or HTTPS reverse proxy can provide a stable reachable address, but the first visit still needs the Farming startup token.
+Open one of the authenticated URLs printed by the command, choose **New Agent**,
+and start a task. See [Getting started](./docs/getting-started.md) for the complete
+first-run flow.
 
 ![Start an Agent](./docs/products/code/assets/02-start-agent-picker.png)
 
@@ -47,67 +44,46 @@ Farming Code is the default desktop and mobile interface. It groups work by proj
 
 ### Agents, Chat, and Terminal
 
-Start or resume Codex, Claude Code, OpenCode, Qoder, and other detected coding CLIs. Supported Agents offer structured Chat for reading results and inspecting tool activity, plus a real Terminal for working directly with the CLI. Search and History cover both current work and resumable sessions.
+Start or resume Codex, Claude Code, OpenCode, Qoder, and other detected coding
+Agents. Use structured Chat to read results and inspect the process, or Terminal
+to work directly with the CLI.
 
 ![Farming Code structured Agent process](./docs/products/code/assets/11-code-agent-process.png)
 
 ### Files and Review
 
-Browse, search, and lightly edit Project Files without leaving the current task. Inspect Git Changes, History, Diff, and Blame, then open a commit or working-copy change in Review.
-
-![Farming Code project files and blame](./docs/products/code/assets/04-files-editor-blame.png)
+Browse, search, and lightly edit Project Files without leaving the current task.
+Inspect changes and open Review when you need evidence.
 
 ### Browser Resources
 
-Each Project can own multiple named Browser Resources. Farming starts a compatible Chromium-based system browser with an isolated profile, streams that exact headless page into the workspace, and sends both human input and Agent actions to the same CDP session. Farming does not download Chromium or depend on Playwright. Agents can discover and operate these resources with `farming browser`; npm installations also expose the `farming-browser` alias.
-
-This first Browser Viewer targets web pages and simple Agent interaction. It is not a replacement for the browser's full window chrome, DevTools, downloads UI, extensions, or Computer Use.
+Farming lets people and Agents use the same project browser. See [Farming Browser](docs/products/code/browser-agent-cli.md).
 
 ## Supported Agents
 
-Farming discovers installed CLIs on the host. Codex, Claude Code, OpenCode, and Qoder support both structured Chat and a native Terminal; other detected coding agents use the Terminal path.
-
 | Agent | Structured Chat | Terminal | History / resume |
 | --- | --- | --- | --- |
 | Codex | Yes | Yes | Yes |
 | Claude Code | Yes | Yes | Yes |
 | OpenCode | Yes | Yes | Yes |
 | Qoder | Yes | Yes | Yes |
-| Qwen Code | — | Yes | CLI-dependent |
-| Aider | — | Yes | CLI-dependent |
-| GitHub Copilot CLI | — | Yes | CLI-dependent |
-| Amazon Q | — | Yes | CLI-dependent |
 | bash / zsh | — | Yes | No |
 
-Farming hosts CLIs that already work on the same machine. It does not replace provider installation, login, or account configuration.
+Provider-backed Agents still require a valid provider login. Other detected CLIs
+must be able to run on the Farming host.
 
 ## Remote Use
 
-Run Farming on the development machine and open its authenticated URL from any desktop or phone that can reach that machine:
-
-```text
-Desktop or phone browser
-          │ HTTP / WebSocket
-          ▼
-Development machine
-  Farming server
-  ├── coding Agent processes
-  ├── real terminals
-  ├── repositories and project files
-  └── optional system-browser processes
-```
-
-The browser can disconnect and reconnect without stopping an Agent. A normal Farming server restart can also reconnect supported live terminal sessions. The desktop layout keeps projects, conversations, files, and review together; the mobile layout focuses one conversation, terminal, or file at a time.
-
-<p align="center">
-  <img src="./docs/products/code/assets/05-mobile-agent-chat.png" alt="Farming Code reconnecting to a running Agent from a phone" width="390">
-</p>
+Run Farming on the development machine and open its authenticated URL from a
+desktop or phone that can reach it. Agents keep running when the browser
+disconnects. See [Operations](./docs/operations/README.md) for remote-access and
+security guidance.
 
 ## Farming CRT
 
 Farming CRT is an optional keyboard-first, retro control-room interface for scanning many Agents, opening their Chat or Terminal sessions, searching history, and viewing usage telemetry.
 
-![Farming CRT multi-Agent control room](./docs/products/crt/assets/01-crt-dashboard.png)
+![Farming CRT multi-agent dashboard](./docs/products/crt/assets/01-crt-dashboard.png)
 
 Code and CRT use the same backend Agents and sessions. Switching interfaces does not create a second Agent. Farming Code remains the default interface and the supported phone interface. See the [Farming CRT guide](./docs/products/crt/README.md) for controls and workflows.
 
@@ -117,65 +93,26 @@ Farming Net is a separate, token-protected directory for Farming deployments. It
 
 ## Installation And Updates
 
-The installed `farming` CLI defaults to port `6694`, base path `/farming`, config directory `~/.farming`, and token authentication. Useful daemon commands are:
+Install with the Quick Start command above. npm installations can update from
+**Settings → Updates**.
 
-```bash
-farming status
-farming url
-farming logs
-farming stop
-```
+![Farming npm update settings](./docs/products/code/assets/14-code-settings.png)
 
-The startup token is stored in `~/.farming/.session-token` and reused across restarts and upgrades. **Settings → Updates** uses a two-step flow for npm installations: **Prepare** installs the selected version into a separate staging directory while the current server keeps running, then **Restart to update** switches the package directory and restarts Farming only after the user clicks it. If the new server does not start, Farming restores the previous package directory. npm preparation first uses the machine's configured registry and retries the registry shown in Settings only when that registry lacks the selected version. Before preparing or applying an update, Farming verifies that npm targets the same package root that launched the server. GitHub Releases also provide standalone CLI and directory bundles; see [GitHub Releases](https://github.com/zhuwenzhuang/farming/releases) for current artifacts.
-
-To run from source with the same port and base path:
-
-```bash
-npm install
-PORT=6694 FARMING_BASE_PATH=/farming npm start
-```
-
-For trusted local development only, `npm run start:no-auth` disables token authentication.
+Standalone CLI and directory bundles remain available from [GitHub Releases](https://github.com/zhuwenzhuang/farming/releases) for manual installation. The in-app updater never reads GitHub Releases; it is available only to npm installations.
 
 ## Security
 
 Farming controls real terminals and files on the development machine. Run it on a trusted host and network. Do not expose it directly to the public internet without a VPN, SSH tunnel, HTTPS reverse proxy, or equivalent access control.
 
-Token authentication protects HTTP and WebSocket traffic. `FARMING_DISABLE_AUTH=1` is only for trusted local development. Workspace file APIs validate paths against the selected project root. See [SECURITY.md](./SECURITY.md) for reporting and deployment guidance.
+See [SECURITY.md](./SECURITY.md) for deployment and reporting guidance.
 
 ## Documentation
 
-- [Farming 2 product overview and capability map](./docs/products/README.md)
-- [Farming Code guide](./docs/products/code/README.md)
-- [Farming CRT guide](./docs/products/crt/README.md)
-- [Farming Net deployment portal](./docs/products/net/README.md)
-- [Mobile guide](./docs/products/code/mobile-guide.md)
-- [ACP runtime](./docs/products/code/acp-runtime.md)
-- [Review foundation](./docs/products/code/review-foundation.md)
+- [Documentation home](./docs/README.md)
+- [Getting started](./docs/getting-started.md)
+- [Operations](./docs/operations/README.md)
 - [Release history](https://github.com/zhuwenzhuang/farming/releases)
-- [Contributor instructions](./AGENTS.md)
-
-## Development Checks
-
-```bash
-npm test
-npm run typecheck
-npm run lint
-FARMING_BASE_PATH=/farming npm run build
-npm run test:e2e:playwright
-```
-
-Product screenshots are generated from an anonymous demo workspace with real browser flows:
-
-```bash
-npm run docs:product:screenshots
-```
-
-To refresh only selected files, pass a comma-separated list:
-
-```bash
-FARMING_SCREENSHOT_FILES=01-code-workspace.png npm run docs:product:screenshots
-```
+- [Contributing](./CONTRIBUTING.md)
 
 ## License
 

package/README.zh_cn.md

@@ -25,19 +25,14 @@ Farming Code 与代码仓库和 Coding CLI 运行在同一台开发机上。Agen
 
 ## 快速开始
 
-准备好 Node.js 22.13 LTS（22.x）或 Node.js 24+，以及至少一个已安装、已登录的受支持 Coding CLI：
+准备好 Node.js 22.13 LTS（22.x）或 Node.js 24+，并确保至少有一个可用的
+Coding Agent Provider：
 
 ```bash
 npm install --global farming-code@latest && farming daemon
 ```
 
-打开命令输出的任意一个带鉴权 URL，选择 **New Agent**，再选择 CLI、Workspace 和 Chat 或 Terminal。关闭浏览器不会停止 Agent；同一个浏览器可以再次打开该地址。在开发机上，下面的命令会重新输出本机地址：
-
-```bash
-farming url
-```
-
-新的远程浏览器应使用 `farming daemon` 启动时输出的带鉴权 **Network** URL。VPN、SSH Tunnel 或 HTTPS Reverse Proxy 可以提供稳定且可达的地址，但第一次访问仍需要 Farming 启动 Token。
+打开命令输出的任意一个带鉴权 URL，选择 **New Agent**，然后启动任务。完整首次使用流程见[快速开始](./docs/getting-started.zh_cn.md)。
 
 ![启动 Agent](./docs/products/code/assets/02-start-agent-picker.png)
 
@@ -47,67 +42,39 @@ Farming Code 是默认的桌面与手机界面。它按项目组织工作，把
 
 ### Agent、Chat 与 Terminal
 
-启动或恢复 Codex、Claude Code、OpenCode、Qoder 以及其他检测到的 Coding CLI。受支持的 Agent 提供结构化 Chat，用来阅读结果和检查工具活动；也可以打开真实 Terminal，直接操作 CLI。Search 和 History 同时覆盖当前工作与可恢复 Session。
+启动或恢复 Codex、Claude Code、OpenCode、Qoder 以及其他检测到的 Coding Agent。使用结构化 Chat 阅读结果和检查过程，或使用 Terminal 直接操作 CLI。
 
 ![Farming Code 结构化 Agent 过程](./docs/products/code/assets/11-code-agent-process.png)
 
 ### Files 与 Review
 
-浏览、搜索并轻量编辑 Project Files，不需要离开当前任务。检查 Git Changes、History、Diff 和 Blame，再把 Commit 或 Working Copy 修改打开到 Review。
-
-![Farming Code 项目文件与 Blame](./docs/products/code/assets/04-files-editor-blame.png)
+浏览、搜索并轻量编辑 Project Files，不需要离开当前任务。需要证据时可以检查修改并打开 Review。
 
 ### Browser Resource
 
-每个 Project 可以拥有多个可命名的 Browser Resource。Farming 使用兼容的 Chromium 系系统浏览器和独立 Profile 启动浏览器，把这个 Headless 页面流式展示在工作区中，并把人的输入和 Agent 操作发送给同一个 CDP Session。Farming 不下载 Chromium，也不依赖 Playwright。Agent 可以通过 `farming browser` 发现并操作这些 Resource；npm 安装还会提供 `farming-browser` 别名。
-
-第一版 Browser Viewer 面向网页展示与简单 Agent 操作，不替代浏览器完整窗口、DevTools、下载界面、浏览器扩展或 Computer Use。
+Farming 让人和 Agent 使用同一个 Project Browser。详见 [Farming Browser](docs/products/code/browser-agent-cli.zh_cn.md)。
 
 ## 支持的 Agent
 
-Farming 会发现开发机上已经安装的 CLI。Codex、Claude Code、OpenCode 和 Qoder 同时支持结构化 Chat 与原生 Terminal；其他检测到的 Coding Agent 使用 Terminal 路径。
-
 | Agent | 结构化 Chat | Terminal | History / Resume |
 | --- | --- | --- | --- |
 | Codex | 是 | 是 | 是 |
 | Claude Code | 是 | 是 | 是 |
 | OpenCode | 是 | 是 | 是 |
 | Qoder | 是 | 是 | 是 |
-| Qwen Code | — | 是 | 取决于 CLI |
-| Aider | — | 是 | 取决于 CLI |
-| GitHub Copilot CLI | — | 是 | 取决于 CLI |
-| Amazon Q | — | 是 | 取决于 CLI |
 | bash / zsh | — | 是 | 否 |
 
-Farming 承载的是已经能在同一台机器正常工作的 CLI，不替代 Provider 的安装、登录和账户配置。
+使用 Provider 的 Agent 仍需要有效登录；其他被发现的 CLI 必须能在 Farming Host 上正常运行。
 
 ## 远程使用
 
-在开发机上运行 Farming，再从能够访问这台机器的电脑或手机打开带鉴权 URL：
-
-```text
-电脑或手机浏览器
-       │ HTTP / WebSocket
-       ▼
-开发机
-  Farming Server
-  ├── Coding Agent 进程
-  ├── 真实 Terminal
-  ├── 代码仓库与项目文件
-  └── 可选的系统浏览器进程
-```
-
-浏览器断开或重新连接不会停止 Agent。Farming Server 正常重启后也可以重新连接受支持的实时 Terminal Session。桌面布局把项目、对话、文件和 Review 放在一起；手机布局一次聚焦一段对话、一个 Terminal 或一个文件。
-
-<p align="center">
-  <img src="./docs/products/code/assets/05-mobile-agent-chat.png" alt="使用手机重新连接仍在运行的 Farming Code Agent" width="390">
-</p>
+在开发机上运行 Farming，再从能够访问这台机器的电脑或手机打开带鉴权 URL。浏览器断开后 Agent 仍会继续运行。远程访问和安全说明见[运行与维护](./docs/operations/README.zh_cn.md)。
 
 ## Farming CRT
 
 Farming CRT 是可选的键盘优先复古控制室，用来扫视多个 Agent、打开它们的 Chat 或 Terminal、搜索 History，以及查看用量遥测。
 
-![Farming CRT 多 Agent 控制室](./docs/products/crt/assets/01-crt-dashboard.png)
+![Farming CRT 多 Agent 仪表盘](./docs/products/crt/assets/01-crt-dashboard.png)
 
 Code 与 CRT 使用相同的后端 Agent 和 Session，切换界面不会创建第二个 Agent。Farming Code 仍是默认界面，也是受支持的手机界面。控制方式和完整流程见 [Farming CRT 指南](./docs/products/crt/README.zh_cn.md)。
 
@@ -117,65 +84,25 @@ Farming Net 是独立、带 Token 鉴权的 Farming 部署目录。它提供一
 
 ## 安装与更新
 
-安装后的 `farming` CLI 默认端口是 `6694`，Base Path 是 `/farming`，配置目录是 `~/.farming`，Token 鉴权默认开启。常用 Daemon 命令：
+按上面的快速开始命令安装即可。npm 安装可以从 **Settings → Updates** 更新。
 
-```bash
-farming status
-farming url
-farming logs
-farming stop
-```
+![Farming npm 更新设置](./docs/products/code/assets/14-code-settings.png)
 
-启动 Token 存放在 `~/.farming/.session-token`，重启和升级会继续复用。**Settings → Updates** 为 npm 安装提供两阶段更新：点击**准备**后，所选版本会安装到独立 staging 目录，当前服务继续运行；准备完成后，只有用户点击**重启并应用**，Farming 才会切换包目录并重启。如果新服务启动失败，Farming 会恢复旧包目录。npm 准备阶段会先使用机器配置的 registry；只有该 registry 缺少所选版本时，才会回退到 Settings 展示版本所用的 registry。准备和应用更新前，Farming 都会校验 npm 目标包根目录与启动当前服务的包根目录一致。GitHub Releases 也提供独立 CLI 和目录 Bundle；当前产物见 [GitHub Releases](https://github.com/zhuwenzhuang/farming/releases)。
-
-从源码运行，并使用相同的端口与 Base Path：
-
-```bash
-npm install
-PORT=6694 FARMING_BASE_PATH=/farming npm start
-```
-
-只有在可信本地开发环境中，才可以用 `npm run start:no-auth` 关闭 Token 鉴权。
+独立 CLI 和目录 Bundle 仍可从 [GitHub Releases](https://github.com/zhuwenzhuang/farming/releases) 手动下载安装。应用内更新不会读取 GitHub Releases，只对 npm 安装开放。
 
 ## 安全
 
 Farming 会控制开发机上的真实终端和文件。请只运行在可信主机和可信网络中，不要在没有 VPN、SSH Tunnel、HTTPS Reverse Proxy 或等价访问控制时直接暴露到公网。
 
-Token 鉴权同时保护 HTTP 和 WebSocket。`FARMING_DISABLE_AUTH=1` 只适合可信本地开发；Workspace 文件 API 会校验所有路径都位于所选项目根目录内。报告和部署说明见 [SECURITY.zh_cn.md](./SECURITY.zh_cn.md)。
+部署与报告说明见 [SECURITY.zh_cn.md](./SECURITY.zh_cn.md)。
 
 ## 文档
 
-- [Farming 2 产品总览与能力矩阵](./docs/products/README.zh_cn.md)
-- [Farming Code 指南](./docs/products/code/README.zh_cn.md)
-- [Farming CRT 指南](./docs/products/crt/README.zh_cn.md)
-- [Farming Net 部署门户](./docs/products/net/README.zh_cn.md)
-- [移动端指南](./docs/products/code/mobile-guide.zh_cn.md)
-- [ACP 运行时](./docs/products/code/acp-runtime.zh_cn.md)
-- [Review 基础](./docs/products/code/review-foundation.zh_cn.md)
+- [文档首页](./docs/README.zh_cn.md)
+- [快速开始](./docs/getting-started.zh_cn.md)
+- [运行与维护](./docs/operations/README.zh_cn.md)
 - [版本历史](https://github.com/zhuwenzhuang/farming/releases)
-- [贡献者说明](./AGENTS.zh_cn.md)
-
-## 开发检查
-
-```bash
-npm test
-npm run typecheck
-npm run lint
-FARMING_BASE_PATH=/farming npm run build
-npm run test:e2e:playwright
-```
-
-产品截图由匿名 Demo Workspace 和真实浏览器流程生成：
-
-```bash
-npm run docs:product:screenshots
-```
-
-只更新指定截图时，可以传入逗号分隔的文件名：
-
-```bash
-FARMING_SCREENSHOT_FILES=01-code-workspace.png npm run docs:product:screenshots
-```
+- [参与贡献](./CONTRIBUTING.zh_cn.md)
 
 ## License
 

package/THIRD_PARTY_NOTICES.md

@@ -15,8 +15,6 @@ preserved in bundled `node_modules` when bundled dependencies are enabled.
 | Package | Version | License | Purpose |
 | --- | --- | --- | --- |
 | `@agentclientprotocol/sdk` | 1.2.1 | Apache-2.0 | ACP JSON-RPC client and protocol types |
-| `@agentclientprotocol/codex-acp` | 1.1.4 | Apache-2.0 | Codex ACP adapter |
-| `@agentclientprotocol/claude-agent-acp` | 0.59.0 | Apache-2.0 | Claude Code ACP adapter |
 | `@modelcontextprotocol/sdk` | 1.29.0 | MIT | Browser Extension MCP server and stdio transport |
 | `@xterm/addon-clipboard` | 0.2.0 | MIT | Browser terminal clipboard integration |
 | `@xterm/addon-fit` | 0.11.0 | MIT | Browser terminal sizing |
@@ -47,12 +45,32 @@ preserved in bundled `node_modules` when bundled dependencies are enabled.
 | `remark-gfm` | 4.0.1 | MIT | GitHub Flavored Markdown support |
 | `remark-math` | 6.0.0 | MIT | Markdown math syntax support |
 | `ripgrep` | 0.3.1 | MIT | Node wrapper for file search support |
+| `tar` | 7.5.19 | BlueOak-1.0.0 | Safe extraction of version-locked startup dependency archives |
 | `ws` | 8.21.0 | MIT | WebSocket server/client support |
 | `yaml` | 2.9.0 | ISC | YAML parsing |
 | `zod` | 3.25.76 | MIT | MCP tool input schema validation |
 
 ## Vendored Assets
 
+Farming builds version- and SHA-256-locked ACP runtime files from these exact
+development dependencies and ships their license texts beside the runtime
+files under `dist/acp/`:
+
+| Package | Version | License | Purpose |
+| --- | --- | --- | --- |
+| `@agentclientprotocol/codex-acp` | 1.1.4 | Apache-2.0 | Reviewed and patched Codex ACP adapter |
+| `@openai/codex` | 0.144.6 | Apache-2.0 | Codex executable discovery and launch bridge; platform CLI binaries are excluded |
+| `@agentclientprotocol/claude-agent-acp` | 0.59.0 | Apache-2.0 | Claude Code ACP adapter |
+| `@anthropic-ai/claude-agent-sdk` | 0.3.207 | Anthropic commercial terms | Claude Agent SDK bridge; platform CLI binaries are excluded |
+
+Before starting a fresh Server, Farming may prepare the exact Codex CLI
+0.144.6, Claude Agent SDK CLI package 0.3.207, and `agent-browser` 0.32.3
+platform artifacts in its private runtime cache. They are not part of the npm
+or application package and remain independent works under their own terms.
+Farming accepts only the version-locked sources and integrity values declared
+by its release manifest. The `agent-browser` license text is included at
+`backend/data/LICENSE.agent-browser`.
+
 Farming vendors `ghostty-web` distribution files under
 `frontend/vendor/ghostty-web` for the optional Ghostty debug renderer. The
 source package is `ghostty-web` 0.4.0, licensed under MIT. Its license is kept
@@ -114,10 +132,11 @@ their code.
 
 Farming can launch or observe coding-agent CLIs installed by the user, including
 OpenCode and the terminal forms of OpenAI Codex CLI and Anthropic Claude Code.
-The optional structured ACP runtime includes the pinned Codex and Claude ACP
-adapter dependency trees, including the provider SDK/runtime packages required
-by those adapters. Those packages remain separate projects governed by their
-own terms and licenses; package-level license files remain in `node_modules`.
+The structured ACP runtime includes reviewed Codex and Claude adapter code, but
+Farming does not bundle a platform Codex or Claude Code CLI inside its package.
+The adapters use the exact system or verified startup-cache executable prepared
+by the Farming launcher. Those tools remain separate projects governed by their
+own terms and licenses.
 
 Farming is not affiliated with, sponsored by, or endorsed by OpenAI, Anthropic,
 Microsoft, or the maintainers of the third-party projects listed above.

package/backend/acp/packaged-claude-acp.js

@@ -0,0 +1,13 @@
+const PACKAGED_CLAUDE_ACP_ARG = '--farming-claude-acp';
+
+async function runPackagedClaudeAcp() {
+  if (!process.pkg) {
+    throw new Error('The packaged Claude ACP entry is available only in a standalone Farming CLI');
+  }
+  throw new Error('The standalone Farming CLI omitted its embedded Claude ACP runtime');
+}
+
+module.exports = {
+  PACKAGED_CLAUDE_ACP_ARG,
+  runPackagedClaudeAcp,
+};

package/backend/acp/packaged-codex-acp.js

@@ -1,10 +1,10 @@
 const PACKAGED_CODEX_ACP_ARG = '--farming-codex-acp';
 
-function runPackagedCodexAcp() {
+async function runPackagedCodexAcp() {
   if (!process.pkg) {
     throw new Error('The packaged Codex ACP entry is available only in a standalone Farming CLI');
   }
-  require('../../dist/acp/codex-acp-1.1.4.js');
+  throw new Error('The standalone Farming CLI omitted its embedded Codex ACP runtime');
 }
 
 module.exports = {

package/backend/acp-runtime.js

@@ -9,9 +9,9 @@ const { promisify } = require('util');
 const packageJson = require('../package.json');
 const { AcpCheckpointStore } = require('./acp-checkpoint-store');
 const { AcpSessionState } = require('./acp-session-state');
-const { readCodexHistoryImageData } = require('./codex-transcript');
 const { AcpClientFileSystem, AcpClientTerminalManager } = require('./acp/client-services');
 const { PACKAGED_CODEX_ACP_ARG } = require('./acp/packaged-codex-acp');
+const { PACKAGED_CLAUDE_ACP_ARG } = require('./acp/packaged-claude-acp');
 const { permissionSecurityWarnings } = require('./acp/permission-security');
 const { patchBlock, rejectPatch } = require('./acp/patch-decisions');
 const { getProviderAdapter, listProviderAdapters } = require('./provider-adapters');
@@ -35,13 +35,23 @@ const CODEX_SET_SESSION_MODEL_METHOD = 'session/set_model';
 const CODEX_STEER_METHOD = '_codex/session/steer';
 const CODEX_ACP_PACKAGE = '@agentclientprotocol/codex-acp';
 const CODEX_ACP_VERSION = '1.1.4';
-const CODEX_ACP_SHA256 = 'e36876cc2250737c719644e6c69ab054a3f8b58071fad45c44407013082942ff';
+const CODEX_ACP_SHA256 = '75e70159692a7889d496651074cd3476687bafb9dc7d4eb3e9590509ad687611';
+const CLAUDE_ACP_PACKAGE = '@agentclientprotocol/claude-agent-acp';
+const CLAUDE_ACP_VERSION = '0.59.0';
+const CLAUDE_ACP_SHA256 = 'a6aa515dd02382617bf46d9eac47b8a1022c6835bcf7a8d61e2c63939be2e49c';
 const CODEX_ACP_VENDOR_ENTRY = path.join(
   __dirname,
   '..',
   'dist',
   'acp',
-  `codex-acp-${CODEX_ACP_VERSION}.js`,
+  `codex-acp-${CODEX_ACP_VERSION}.mjs`,
+);
+const CLAUDE_ACP_VENDOR_ENTRY = path.join(
+  __dirname,
+  '..',
+  'dist',
+  'acp',
+  `claude-agent-acp-${CLAUDE_ACP_VERSION}.mjs`,
 );
 const execFileAsync = promisify(execFile);
 
@@ -70,6 +80,15 @@ function adapterEntry(packageName) {
   if (packageName === CODEX_ACP_PACKAGE && fs.existsSync(CODEX_ACP_VENDOR_ENTRY)) {
     return verifiedCodexAcpEntry(CODEX_ACP_VENDOR_ENTRY);
   }
+  if (packageName === CLAUDE_ACP_PACKAGE && fs.existsSync(CLAUDE_ACP_VENDOR_ENTRY)) {
+    const actualSha256 = fileSha256(CLAUDE_ACP_VENDOR_ENTRY);
+    if (actualSha256 !== CLAUDE_ACP_SHA256) {
+      throw new Error(
+        `Claude ACP runtime failed integrity verification: expected ${CLAUDE_ACP_SHA256}, found ${actualSha256}`,
+      );
+    }
+    return CLAUDE_ACP_VENDOR_ENTRY;
+  }
   let sdkDirectory;
   try {
     sdkDirectory = path.dirname(runtimeRequire.resolve('@agentclientprotocol/sdk'));
@@ -109,7 +128,11 @@ function resolveAcpLaunch(provider, options = {}) {
     const launch = nodeAdapterLaunch(
       adapterEntry(adapter.acp.packageName),
       options.runtimeEnv || process.env,
-      adapter.acp.packageName === CODEX_ACP_PACKAGE ? PACKAGED_CODEX_ACP_ARG : '',
+      adapter.acp.packageName === CODEX_ACP_PACKAGE
+        ? PACKAGED_CODEX_ACP_ARG
+        : adapter.acp.packageName === CLAUDE_ACP_PACKAGE
+          ? PACKAGED_CLAUDE_ACP_ARG
+          : '',
     );
     return { ...launch, version: adapter.acp.version };
   }
@@ -833,19 +856,6 @@ class AcpRuntime extends EventEmitter {
             binding.historyReplayActive = false;
           }
           binding.sessionState.finishHistoryReplay();
-          if (provider === 'codex' && binding.sessionState.hasCodexHistoryImageReferences()) {
-            let imageDataByPath = new Map();
-            try {
-              imageDataByPath = await readCodexHistoryImageData(requestedSessionId, {
-                codexHome: binding.env.CODEX_HOME,
-              });
-            } catch {
-              // Local history images can still be restored from their adapter paths.
-            }
-            this.requireOpenBinding(binding);
-            await binding.sessionState.hydrateCodexHistoryAttachments({ imageDataByPath });
-            this.requireOpenBinding(binding);
-          }
           this.restorePatchDecisions(binding, restoredCheckpoint?.patchDecisions);
           historyMode = 'load';
           opened = true;
@@ -2508,6 +2518,17 @@ class AcpRuntime extends EventEmitter {
     return visible;
   }
 
+  getTranscriptEntry(agentId, entryId) {
+    const binding = this.requireBinding(agentId);
+    const entries = (binding.sessionState?.entries || []).filter(candidate => (
+      String(candidate?.id || '') === String(entryId || '')
+    ));
+    if (entries.length !== 1) return null;
+    const [entry] = entries;
+    if (!entry || binding.sessionState.isInternalEntry(entry)) return null;
+    return entry;
+  }
+
   getPatchDecision(agentId, toolCallId, requestedPath) {
     const binding = this.requireBinding(agentId);
     return binding.patchDecisions.get(`${String(toolCallId || '')}\n${String(requestedPath || '')}`) || '';