@harness-mix/cli 0.1.3

package/CHANGELOG.md

@@ -0,0 +1,19 @@
+# Changelog
+
+## 0.1.3 — 2026-09-13
+
+- Added multi-agent collaboration support (@ mentions composer, thread delegation, worktree isolation).
+- Cleaned up legacy standalone workbench UI services, throwaway HTML prototypes, and unused icon assets.
+- Enhanced native harness adapters and settings management.
+
+## 0.1.2 — 2026-09-13
+
+- Hardened native process supervision, DPAPI secret store, and dual-channel auto-update.
+
+
+- Added native ACP adapters for CodeBuddy, Kiro CLI, Cursor CLI and Qoder.
+- Added explicit ACP bridge configuration for ZCode and Trae without claiming an unverified vendor entry point.
+- Renamed WorkBuddy to CodeBuddy while preserving legacy task, history and preference identifiers.
+- Added image capability negotiation, bounded ACP event draining, idle/hard turn timeouts, cancellation fallback and stuck-tool diagnostics.
+- Added durable multi-agent recovery checkpoints and verified DSH → CodeBuddy collaboration.
+- Updated the README and native integration documentation with installation, verification and capability limits.

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,14 @@
+Harness Mix
+
+Copyright 2026 Harness Mix contributors
+
+This product includes software developed by third-party open source projects.
+Third-party components remain subject to their respective licenses.
+
+Native Codex Desktop components (renderer-extension, desktop-control, shared-contracts)
+are derived from BytePioneer-AI/codex-host v0.6.1 under the MIT License.
+Copyright (c) 2026 BytePioneer-AI.
+Source: https://github.com/BytePioneer-AI/codex-host
+All execution runtimes, protocols, adapters and local launchers are developed and maintained in this repository.
+
+Native DeepSeek integration uses @deepseek-ai/dsh 0.1.2-rc.1 (MIT).

package/README.md

@@ -0,0 +1,262 @@
+# Harness Mix
+
+macOS/Linux 已加入源码构建与启动适配（待目标系统真机验收）；安装方式、Linux 桌面前提和支持边界见 [跨平台指南](docs/cross-platform.md)。
+
+<p align="center">
+  <img src="src/assets/brand-harness-mix.png" width="92" alt="Harness Mix logo">
+</p>
+
+<p align="center">
+  ⭐ 如果这个项目对你有帮助，请给我们一个 <a href="https://github.com/emo-xiaoyu/harness-mix">Star</a>！ ⭐
+</p>
+
+<p align="center"><strong>Codex 原生 UI，连接多个原生 Coding Harness。</strong></p>
+
+<p align="center">
+  <a href="LICENSE"><img alt="License: Apache-2.0" src="https://img.shields.io/badge/license-Apache--2.0-blue.svg"></a>
+  <img alt="UI" src="https://img.shields.io/badge/UI-Codex%20Desktop-412991.svg">
+  <img alt="Platform" src="https://img.shields.io/badge/platform-Windows-0078D4.svg">
+</p>
+
+<p align="center"><strong>当前注册的 Harness（16 个）</strong></p>
+
+<table align="center">
+  <tbody>
+    <tr>
+      <td align="center"><img src="src/assets/icons/antigravity-color.svg" width="28" height="28" alt="Antigravity"><br><sub>Antigravity</sub></td>
+      <td align="center"><img src="src/assets/icons/codex-harness.svg" width="28" height="28" alt="Codex"><br><sub>Codex</sub></td>
+      <td align="center"><img src="src/assets/icons/claude-color.svg" width="28" height="28" alt="Claude Code"><br><sub>Claude Code</sub></td>
+      <td align="center"><img src="src/assets/icons/pi.svg" width="28" height="28" alt="Pi"><br><sub>Pi</sub></td>
+    </tr>
+    <tr>
+      <td align="center"><img src="src/assets/icons/omp-color.svg" width="28" height="28" alt="Oh My Pi"><br><sub>Oh My Pi</sub></td>
+      <td align="center"><img src="src/assets/icons/deepseek-color.svg" width="28" height="28" alt="DeepSeek Harness"><br><sub>DeepSeek</sub></td>
+      <td align="center"><img src="src/assets/icons/opencode-color.svg" width="28" height="28" alt="OpenCode"><br><sub>OpenCode</sub></td>
+      <td align="center"><img src="src/assets/icons/grok-color.svg" width="28" height="28" alt="Grok"><br><sub>Grok</sub></td>
+    </tr>
+    <tr>
+      <td align="center"><img src="src/assets/icons/openclaw-color.svg" width="28" height="28" alt="OpenClaw"><br><sub>OpenClaw</sub></td>
+      <td align="center"><img src="src/assets/icons/hermes-color.svg" width="28" height="28" alt="Hermes"><br><sub>Hermes</sub></td>
+      <td align="center"><img src="src/assets/icons/qoder-color.svg" width="28" height="28" alt="Qoder"><br><sub>Qoder</sub></td>
+      <td align="center"><img src="src/assets/icons/codebuddy-color.svg" width="28" height="28" alt="CodeBuddy"><br><sub>CodeBuddy</sub></td>
+    </tr>
+    <tr>
+      <td align="center"><img src="src/assets/icons/kiro-cli-color.svg" width="28" height="28" alt="Kiro"><br><sub>Kiro</sub></td>
+      <td align="center"><img src="src/assets/icons/cursor.svg" width="28" height="28" alt="Cursor"><br><sub>Cursor</sub></td>
+      <td align="center"><img src="src/assets/icons/zcode-color.svg" width="28" height="28" alt="ZCode"><br><sub>ZCode</sub></td>
+      <td align="center"><img src="src/assets/icons/trae-color.svg" width="28" height="28" alt="Trae"><br><sub>Trae</sub></td>
+    </tr>
+  </tbody>
+</table>
+
+<p align="center"><sub>图标与 Harness 能力均来自项目自身的注册表；只有本机已安装且握手成功的 Harness 才会进入真实运行。</sub></p>
+
+Harness Mix 是接入官方 Codex Desktop 原生界面的本地内核。它通过本地编译的 CLI Shim 对接桌面的 app-server 协议，把包括 Antigravity、Codex、Pi、Oh My Pi、Claude Code、DeepSeek Harness、OpenCode、Grok、OpenClaw、Hermes、Qoder、CodeBuddy、Kiro CLI、Cursor CLI、ZCode 和 Trae 在内的原生 Coding Harness 接入同一套 UI。Host Runtime 与 Protocol Core 管理任务映射、协作和事件投影；模型调用、工具执行、原生会话与凭据仍由各 Harness 自己管理。
+
+## 界面预览
+
+<p align="center">
+  <img src="docs/images/codex-desktop-home.png" width="960" alt="Codex Desktop 原生首页中的 Harness Mix">
+</p>
+
+预览来自当前 Codex Desktop 原生窗口：Harness Mix 作为原生扩展入口出现在桌面工具栏和 Composer 中，会话、模型、工具与权限仍由 Codex Desktop 及各 Harness 管理。
+
+## 能做什么
+
+- 在 Codex Desktop 原生输入框中选择 Harness 并发起会话。
+- 流式呈现回答、思考、命令执行、工具调用、文件变更和上下文压缩。
+- 调用每个 Harness 原生提供的模型、权限、上下文用量和快捷指令。
+- 会话中原地切换 Harness（`/switch <Harness 名> [备注]` 或 `codexhost/thread/harness/switch`）：会话历史与文件现场保留在 Host 线程上，切换后首轮自动携带一次性上下文信封；切回旧 Harness 时按其原生机制（Pi `--session` / Claude `resume`）恢复原会话。
+- 原生 Diff、审批与提问组件直接渲染，审批路由回原生 Harness，不代替用户作出权限决定。
+- CodeBuddy、Kiro 和 Cursor 使用原生 ACP 加厂商专用接口：提问、计划确认、配置确认、取消恢复、上下文与历史按各自协议处理。功能和验证范围见下表，不将通用 ACP 能力视为所有 CLI 都已支持。
+- 通过 Adapter 注册新 Harness，UI 侧无需理解厂商协议。
+
+<p align="center">
+  <img src="docs/images/codex-desktop-session.png" width="960" alt="Codex Desktop 原生会话中的 Harness Mix">
+</p>
+
+## 原生接入
+
+通过 Codex Desktop 内的 Harness 选择器统一查看连接、筛选模型和保存每个 Harness 的新对话默认模型。具体流程与原生边界见 [Harness 管理说明](docs/harness-management.md)。
+
+| Harness | 原生接口 | 当前接入重点 |
+| --- | --- | --- |
+| Antigravity | `agy` CLI (`stream-json` / PreToolUse Hook) | 流式输出、Gemini 模型目录与思考档位、Desktop 审批与提问桥接、文件变更、配额查询与 Fork |
+| Codex | `codex app-server --stdio` | Thread / Turn / Item、流式事件、审批、Usage、Resume、Fork、Compact |
+| Pi | `pi --mode rpc` | 会话恢复、模型目录、Usage、原生命令、Fork |
+| Oh My Pi | `omp --mode rpc`（Pi 家族协议，见 `pi-family.js`） | 与 Pi 同源：会话、模型、思考档位、权限、Fork、Usage |
+| Claude Code | `@anthropic-ai/claude-agent-sdk` 的 `query()` | 持久会话、流式消息、工具、权限、模型与 Resume |
+| DeepSeek Harness | 普通任务 `npm run dsh -- web`；协作主任务 `npm run dsh -- --profile acp` | Web Remote/Typert RPC；主任务使用官方 ACP 的会话级 MCP；WebSocket 事件、会话与模型控制 |
+| OpenCode | `opencode serve`（原生 HTTP / SSE，见 `opencode.js`） | 会话、模型目录、权限模式、图片、Fork |
+| Grok | `grok agent stdio`（独立适配 ACP 基础消息与 `_x.ai/*` 厂商扩展，见 `grok.js`） | 会话、模型、思考档位、原生命令目录、Token Usage、原生 Fork |
+| OpenClaw | 本机 Gateway loopback WebSocket（`openclaw-gateway.js` + `openclaw.js`） | 会话与恢复、流式增量、工具与命令输出、exec/plugin 审批回路由、模型与思考档位逐轮覆盖 |
+| Hermes | `hermes acp`（ACP over stdio，共享 `acp.js` 工厂） | 会话持久化/恢复/Fork、流式回答与思考、工具、审批、模型选择 |
+| Qoder | `qodercli --acp` / `qoder --acp`（官方 CLI，`native-acp.js`） | 原生会话、配置、审批、工具、恢复；图片按握手能力启用 |
+| CodeBuddy | `codebuddy --acp` + `_codebuddy.ai/*` | 原生提问与提交重试、审批作用范围、取消后重连恢复、模型/思考/模式、原生历史导入、去重 Token/Credits |
+| Kiro CLI | `kiro-cli acp --agent-engine v3 --auth-method cli` + `_kiro/*` | 原生提问、带作用范围的 consent、模型/effort、上下文查询、原生压缩与 fork（后两项需握手支持） |
+| Cursor CLI | `cursor-agent acp` + `cursor/*` | 单选/多选提问、计划接受/拒绝、原生模型变体/模式、会话恢复、完成后的 Diff 投影 |
+| ZCode | 需显式配置兼容 ACP 桥接程序（尚未验证） | 本机 0.16.5 仅确认 `app-server --stdio`；不能直接作为 ACP 启动 |
+| Trae | 需显式配置兼容 ACP 程序（尚未验证） | 官方 trae-agent 未发现 ACP 入口；不再使用猜测的启动/安装命令 |
+
+CodeBuddy、Kiro CLI、Cursor CLI、Qoder、ZCode 和 Trae 均已接入默认选择器、模型偏好、侧栏图标与共享 ACP 引擎；其中只有已安装且握手成功的 Harness 才会进入真实运行。原 Workbuddy 已更名为 CodeBuddy；旧任务、切换历史、模型偏好与名称别名保留兼容。DSH 协作主任务也使用官方 ACP，普通任务继续使用 Web Remote。
+
+2026-09-12 健康检查：Pi、DSH、Claude Code、Codex、Grok、CodeBuddy 的真实文本回路通过；OpenCode 被账户余额阻断，Qoder 被 Credits 额度阻断，OMP、Hermes、Kiro、Cursor 本机未安装。图片真实回路通过 Antigravity、Pi、Claude Code、Codex、Grok、CodeBuddy；DSH 与 OpenClaw 的当前模型拒绝图片，Qoder/OpenCode 分别被额度/余额阻断。ZCode、Trae 目前只有显式 ACP 桥接配置入口，未证明官方 CLI 提供 ACP 服务。报告见 [`output/harness-health/1789191914230/report.json`](output/harness-health/1789191914230/report.json) 和 [`output/harness-health/1789191791797/report.json`](output/harness-health/1789191791797/report.json)；完整安装与边界见 [原生 ACP 深度适配](docs/native-acp.md)。
+
+能力只在 Adapter 的 `manifest` 中声明。界面根据真实能力显示入口，不靠 Harness 名称猜测功能；厂商特有字段会保留在原生引用和载荷中。
+
+## 架构
+
+```mermaid
+flowchart TB
+  Desktop[Codex Desktop 原生 UI] --> Shim[Harness Mix CLI Shim]
+  Shim --> Host[原生 Host 入口 src/main/native]
+  Host --> Runtime[Host Runtime]
+  Runtime --> Core[Protocol Core]
+  Runtime --> Store[(Thread and session store)]
+  Runtime --> Registry[Adapter registry]
+  Registry --> Antigravity[Antigravity CLI]
+  Registry --> Codex[Codex app-server]
+  Registry --> Pi[Pi RPC]
+  Registry --> OMP[Oh My Pi RPC]
+  Registry --> Claude[Claude Agent SDK]
+  Registry --> DSH[DSH Web Remote]
+  Registry --> OpenCode[OpenCode Server HTTP / SSE]
+  Registry --> Grok[Grok native stdio + vendor extensions]
+  Registry --> OpenClaw[OpenClaw Gateway loopback WS]
+  Registry --> Hermes[Hermes ACP stdio]
+  Registry --> Qoder[Qoder ACP stdio]
+  Registry --> CodeBuddy[CodeBuddy ACP + native extensions]
+  Registry --> Kiro[Kiro ACP + native extensions]
+  Registry --> Cursor[Cursor ACP + native extensions]
+  Registry --> ZCode[ZCode 显式 ACP 桥接入口 未验证]
+  Registry --> Trae[Trae 显式 ACP 入口 未验证]
+```
+
+```text
+src/
+├─ main/
+│  ├─ adapters/          # 每个 Harness 的原生适配器
+│  ├─ harness-adapter/   # Manifest、能力与适配器契约
+│  ├─ host/              # 编排、恢复、持久化与事件投影
+│  ├─ native/            # 原生模式：Launcher、Shim、Host 入口、协议桥
+│  └─ protocol-core/     # Thread / Turn / Item 统一语义
+├─ native-ui/
+│  ├─ renderer-extension/  # 注入 Codex Desktop 的渲染扩展（选择器、模型目录）
+│  ├─ desktop-control/     # CDP 控制器与请求桥
+│  └─ shared-contracts/    # 渲染侧与内核共享的协议契约
+└─ assets/icons/         # Harness 与模型图标（编译期嵌入）
+```
+
+新增 Harness 时，实现同形 Adapter 并注册到 `src/main/adapters/index.js`。核心形态如下：
+
+```js
+module.exports = {
+  manifest: {
+    id,
+    name,
+    icon,
+    capabilities: { streaming, tools, approvals, models, resume, fork, usage }
+  },
+  create(emit) {
+    return {
+      inspect,
+      open,
+      send,
+      cancel,
+      close,
+      respond,
+      listModelsFor,
+      setModel,
+      fork
+    };
+  }
+};
+```
+
+## 本地运行
+
+开发环境需要 Windows、近期 Node.js LTS 和 npm。应用不会读取或保存 Harness 的账户密钥，请先在对应的原生 CLI 中完成安装与登录。
+
+```powershell
+git clone https://github.com/emo-xiaoyu/harness-mix.git
+cd harness-mix
+npm install
+```
+
+### 从 npm 安装
+
+Harness Mix 发布为 `@harness-mix/cli` npm 包，命令名仍是 `harness-mix`。当前发布包包含本次构建平台的 native Shim；macOS/Linux 请在目标系统执行源码构建，完整说明见 [跨平台指南](docs/cross-platform.md)。
+
+```powershell
+npm install --global @harness-mix/cli
+harness-mix
+```
+
+升级到最新版本：
+
+```powershell
+npm update --global @harness-mix/cli
+```
+
+首次运行会重启已打开的 Codex Desktop。npm 包只分发 Harness Mix 本身；各 Harness 的 CLI、登录状态、模型额度和权限仍需按下表在本机单独安装和配置。
+
+### 运行方式
+
+原生模式（默认）：本地编译的 Shim 与 Renderer 扩展接入官方 Codex Desktop，模型选择会路由到对应 Harness。首次启动会重启已打开的 Codex Desktop：
+```powershell
+npm start
+```
+
+常用原生依赖：
+
+- Codex：安装 `@openai/codex`，确保 `codex` 命令可用。
+- Pi：确保 `pi.cmd` 可用。
+- Claude Code：SDK 已由 npm 依赖安装，认证仍由 Claude Code 环境管理。
+- DeepSeek Harness：使用本项目锁定的 `@deepseek-ai/dsh@0.1.2-rc.1`。可通过 `HARNESS_MIX_DSH_ROOT` 显式指定源码目录，但版本必须被内核支持。
+- CodeBuddy：安装官方 `codebuddy` CLI 并完成登录；旧 WorkBuddy 安装也可通过兼容别名继续使用。
+- Kiro CLI：安装 `kiro-cli`，启用 `acp` 子命令并完成 CLI 登录。
+- Cursor CLI：安装 `cursor-agent` 并完成 CLI 登录。
+- Qoder：安装 `qodercli`（或 `qoder`）并完成 CLI 登录；ACP 入口由本机版本决定。
+- ZCode / Trae：只有在拥有已验证的 ACP 兼容桥接程序时才配置 `HARNESS_MIX_ZCODE_ACP_EXECUTABLE` / `HARNESS_MIX_TRAE_EXECUTABLE`，项目不会猜测官方入口。
+
+原生接入方式、数据目录和验证说明见 [原生 Codex 接入](docs/native-codex.md)。
+
+## 验证
+
+```powershell
+npm run check
+npm run test:core-all
+npm run e2e:native
+npm run smoke:native-ui
+```
+
+涉及原生 Adapter 时，再执行对应的真实链路：
+
+```powershell
+npm run e2e:pi
+npm run e2e:dsh
+npm run e2e:claude
+npm run e2e:codex
+```
+
+部分 E2E 会启动真实 Harness，可能需要本机安装、登录或模型额度。测试生成物写入 `output/`，不应提交到仓库。
+
+## 设计原则
+
+1. **原生能力优先**：Adapter 翻译协议，不重新实现 Harness。
+2. **诚实声明能力**：只有完成接线和验证的能力才进入 `manifest`。
+3. **惰性恢复**：打开历史任务只读取本地投影，发送新消息时才恢复原生进程。
+4. **可回放事件**：Core Event 保持稳定顺序，可用于恢复、投影和确定性校验。
+5. **凭据隔离**：账号、令牌、沙箱和权限决定由原生程序管理。
+
+## 项目状态
+
+- [内核迁移状态](CORE-MIGRATION-STATUS.md)
+- [下一步计划](NEXT-STEPS.md)
+- [Codex Desktop 原生接入说明](docs/native-codex.md)
+
+Harness Mix 参考了 [codex-host](https://github.com/BytePioneer-AI/codex-host) 的插件化组织方式，并使用 [OpenAI Codex](https://github.com/openai/codex) 官方 app-server 协议完成 Codex 原生接入。
+
+## License
+
+Harness Mix 基于 [Apache License 2.0](LICENSE) 发布。第三方组件仍适用各自的许可证；归属信息见 [NOTICE](NOTICE)。

package/Start-Codex.cmd

@@ -0,0 +1,5 @@
+@echo off
+title Harness Mix - Codex Native Launcher
+cd /d "%~dp0"
+call npm.cmd run start:codex
+pause

package/config/codex-desktop-compatibility.json

@@ -0,0 +1,29 @@
+{
+  "schemaVersion": 1,
+  "contractVersions": {
+    "rendererBinding": 1,
+    "controllerReadiness": 2,
+    "protocolFixture": 1
+  },
+  "blockedDesktopVersions": [],
+  "evidence": [
+    {
+      "desktopVersion": "26.721.4979.0",
+      "level": "protocol-fixture",
+      "checkedAt": "2026-07-25",
+      "notes": "Sanitized official app-server envelope capture; not a full Desktop UI acceptance."
+    },
+    {
+      "desktopVersion": "26.901.2854.0",
+      "level": "protocol-and-smoke",
+      "checkedAt": "2026-09-11",
+      "notes": "Install inspection, protocol suite, native build and offscreen Electron smoke passed; full restarted Desktop acceptance remains pending."
+    },
+    {
+      "desktopVersion": "26.908.4834.0",
+      "level": "desktop-e2e",
+      "checkedAt": "2026-09-13",
+      "notes": "Restarted isolated Desktop acceptance passed with the 26.908 connection snapshot and draft identity contracts: Renderer request bridge ready, native input editable, Pi selected with its model, external turn routed through Harness Mix HostRuntime, and exact live Pi response rendered."
+    }
+  ]
+}

package/docs/chatgpt-web-sidebar.md

@@ -0,0 +1,27 @@
+# ChatGPT 网页侧边对话
+
+> 历史设计记录：当前 Harness Mix 原生模式不包含下文所述的 `side-chat` / `web-chat` 实现，相关源码和 `smoke:web-chat` 入口已不在当前仓库中。本文仅保留方案边界，不能作为当前功能或可执行验收说明。
+
+## 官方实现参考
+
+2026-09-09 核对 `openai/codex` main（`9ba1d9eb5bbbd87ba2fc528d91ad239eea975ee9`）的完整目录树、README、`codex-rs/chatgpt` 与桌面启动器后，未发现截图中 Quick chat 面板的前端与聊天历史同步实现。
+
+- [官方 ChatGPT 使用文档](https://learn.chatgpt.com/docs/use-chatgpt)明确说明：Codex 的 Quick chat 可以访问网页和手机端的 ChatGPT 聊天。
+- [公开组件列表](https://learn.chatgpt.com/docs/open-source)列出 CLI、SDK、App Server 等；没有提供该面板的源码入口。
+- [`codex-rs/chatgpt/src/get_task.rs`](https://github.com/openai/codex/blob/9ba1d9eb5bbbd87ba2fc528d91ad239eea975ee9/codex-rs/chatgpt/src/get_task.rs)读取 `/wham/tasks/{task_id}` 编码任务，不是网页聊天列表。
+- [`codex-rs/cli/src/desktop_app/windows.rs`](https://github.com/openai/codex/blob/9ba1d9eb5bbbd87ba2fc528d91ad239eea975ee9/codex-rs/cli/src/desktop_app/windows.rs)负责启动或安装桌面应用，不包含 Quick chat UI。
+
+因此这里实现的是直接内嵌 ChatGPT 官方网页的替代接入，不声称复制了官方 Quick chat 的内部实现。最近聊天与模型菜单使用网页自身的界面，不伪造官方内部会话接口。
+
+点击“新建对话”旁的聊天按钮或 Alt+S，打开内嵌的 https://chatgpt.com/。
+首次使用在网页中登录。网页使用独立的持久浏览器会话，关闭面板后重新打开保留页面；应用重启后可通过网页历史记录继续聊天。
+
+侧边聊天直接使用 ChatGPT 网页，不调用 Codex app-server，不占用 Codex 编码额度。ChatGPT 网页自身的模型与使用限制仍适用。将内容添加到主输入框后，再发送给编码 Harness，会按该 Harness 正常计费或消耗额度。
+
+“添加到当前 Harness”优先导入网页选中文字；未选择时读取当前页面已加载的用户与助手消息文本，附带页面标题和来源链接。只填入草稿，由用户点击发送。图片附件不会自动下载或导入；网页未加载的历史消息也不会导入。网页结构变化导致读取失败时会显示提示，可选中文字重试。
+
+登录和模型选择使用网站原生界面。浏览器会话由 Electron 管理；应用不读取、导出或代理 Cookie、Token。远程页面启用 sandbox、contextIsolation，关闭 nodeIntegration，不注入本地 IPC preload。登录弹窗使用相同浏览器会话。
+
+实现：`src/main/side-chat/web.js`、`src/renderer/web-chat.js`、`src/renderer/web-chat.css`。原 app-server 侧边模块保留在源码中，但生产入口和 preload 已停止接入它。
+
+历史版本曾使用 `smoke:web-chat` 验证隔离网页夹具；当前版本没有该命令。若未来恢复此能力，必须同时恢复隔离、安全边界测试以及真实登录后的人工验收。

package/docs/cross-platform.md

@@ -0,0 +1,73 @@
+# macOS / Linux 适配设计与运行
+
+保留 Launcher → Shim → HostRuntime → ProtocolCore → native Harness → 原生 Codex UI。平台差异集中在 `src/main/native/platform.js`，不引入独立桌面 UI，不改变模型、工具、登录和审批的所有权。
+
+## 支持范围
+
+| 层 | Windows | macOS | Linux |
+| --- | --- | --- | --- |
+| 安装元数据 | x64 / arm64 | x64 / arm64 | x64 / arm64 |
+| Shim 构建 | Rust + AppX/DPAPI helpers | 本机 Rust Shim | 本机 Rust Shim |
+| 桌面发现 | AppX | `/Applications/Codex.app`、`~/Applications/Codex.app` | 显式指定已安装的兼容桌面可执行文件 |
+| 启动 | AppX 环境注入 | 直接执行 `.app/Contents/MacOS` | 直接执行 Electron 桌面二进制 |
+| 本项目 secret helper | DPAPI | 明确不可用 | 明确不可用 |
+| 实际桌面验收 | 见版本兼容性清单 | 待真机验收 | 待兼容桌面和真机验收 |
+
+安装元数据表示允许安装和本机构建，不表示所有 CPU、桌面版本及所有 Harness 已通过验收。macOS/Linux 当前使用源码安装；不要把 Windows 的 `.exe` 或另一 CPU 架构的 Shim 复制过去。现有 npm 全局安装的预编译分发仍以 Windows 为主，尚未提供各系统/架构的独立发布包。
+
+Linux 启动支持有前提：必须自行安装支持 `CODEX_CLI_PATH`、app-server 和 CDP 的兼容 Electron 桌面。本项目没有捆绑 Linux Codex Desktop，也不保证官方 Linux 桌面可用。无兼容桌面时可以构建和运行内核/协议测试，不能启动原生 UI。请使用实际可执行文件路径，不使用 `.desktop` 文件、启动脚本或 AppImage 外层包装器。
+
+## macOS 安装
+
+安装 Node.js 22.19+（22.x）或 24.x、Rust stable、Git 和 Codex Desktop。Apple Silicon 使用 arm64 Node/Rust；Intel 使用 x64。先用各 Harness 自己的命令完成安装和登录。
+
+```sh
+git clone https://github.com/emo-xiaoyu/harness-mix.git
+cd harness-mix
+npm ci
+npm run build:native
+npm run test:platform
+npm run test:shim
+npm run check:native
+# 完全退出已有 Codex Desktop 后启动
+npm start -- --no-update
+```
+
+非标准安装目录，在上述检查与启动前设置：
+
+```sh
+export HARNESS_MIX_DESKTOP_APP="/absolute/path/Codex.app"
+```
+
+启动器读取 Info.plist 的可执行文件名和版本，默认使用 `Contents/Resources/codex`。CLI 布局不同时设置 `CODEXHOST_STOCK_CODEX_PATH`，必须指向桌面自带的原版 CLI，不能指向 Harness Mix Shim。不改写签名包，不关闭 Gatekeeper。CLI 工具需在启动终端的 PATH 中可用。
+
+## Linux 安装
+
+安装同样的 Node、Rust、Git，以及系统 `ps`（通常由 procps 提供）和 `tar`。桌面启动需要可用的图形会话及该 Electron 应用的系统依赖。
+
+```sh
+npm ci
+npm run build:native
+export HARNESS_MIX_DESKTOP_EXECUTABLE="/absolute/path/to/desktop-binary"
+export CODEXHOST_STOCK_CODEX_PATH="/absolute/path/to/resources/codex"
+# 填写真实桌面版本，不是 CLI 版本；未知时省略，兼容性显示 unverified
+export HARNESS_MIX_DESKTOP_VERSION="1.2.3"
+npm run check:native
+npm start -- --no-update
+```
+
+## 平台行为
+
+- 数据目录：Windows 延续 `%APPDATA%/harness-mix/codexhost`；macOS 使用 `~/Library/Application Support/harness-mix/codexhost`；Linux 使用 `$XDG_DATA_HOME/harness-mix/codexhost`，默认 `~/.local/share/harness-mix/codexhost`。`CODEXHOST_DATA_DIR` 始终优先。历史 Unix 试用数据如在其他目录，需显式设置该变量；不会自动搬迁。
+- macOS/Linux 要求先退出已运行的同一个桌面程序，避免 Electron 单实例复用丢失 Shim 环境。不会按程序名批量清理用户进程。
+- Unix Shim 使用 `exec` 替换自己，保留 PID、stdio 和信号；正常关闭依赖 Host 的 EOF/SIGTERM 清理。停止 Harness 时按父子关系清理子进程。Unix 不宣称具备 Windows Job Object 在 `SIGKILL` 下的强制整树退出保证；已经脱离父进程的 daemon 不属于该保证。
+- Grok、Hermes 的 Unix 默认命令去掉 `.exe`；DSH Web 模式在 Unix 使用 `npm`，必须配置 `HARNESS_MIX_DSH_ROOT`。其他 Harness 仍需其厂商提供相应系统的原生 CLI，不将协议适配等同于厂商跨平台支持。
+- Windows 的旧兼容性记录只对 Windows 生效。macOS/Linux 未有同平台 `desktop-e2e` 证据时，`HARNESS_MIX_STRICT_COMPATIBILITY=1` 会拒绝启动。`check:native` 仅检查安装和构建产物，不代表真实 UI 验收。
+- 本次覆盖本地桌面启动。继承的 Remote Control 桥接仍含 Windows 描述文件和 PowerShell 启动逻辑，不属于 macOS/Linux 支持范围。
+- `npm run diagnostics` 在 Windows 输出 zip，在 macOS/Linux 输出 tar.gz。凭据仍归原生 Harness 管理，无新增凭据存储。
+
+## 验证与发布门槛
+
+CI 增加 Windows/macOS/Linux 的 Node 22/24 内核测试和本机构建，真实 Shim fixture 检查路由、Unicode、带空格参数、环境变量及 EOF；这些不需要账户。配置 CI 不等于已执行 CI。当前 Windows 开发机不能代替 macOS/Linux 真机结果。
+
+在每种目标 OS/CPU 上运行 `npm run check`、`npm run test:core-all`、`npm run build:native`、`npm run test:platform`、`npm run test:shim`、`npm run e2e:native`，再启动真实桌面，逐个验证所需 Harness 的模型列表、Thinking、流式工具输出、原生审批、取消、历史恢复及退出清理。记录 OS、CPU、桌面版本和证据后，才能增加该平台的 `desktop-e2e` 记录。后续发布矩阵需要覆盖 macOS Intel/Apple Silicon、Linux x64/arm64，不能用单个平台的构建文件混发。