harness-mix 0.1.0

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,184 @@
+# Harness Mix
+
+<p align="center">
+  <img src="src/assets/brand-harness-mix.png" width="92" alt="Harness Mix logo">
+</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>
+
+Harness Mix 是接入官方 Codex Desktop 原生界面的本地内核：通过本地编译的 CLI Shim 接管桌面的 app-server 协议，把 Pi、Claude Code、DeepSeek Harness、Antigravity 和 Codex 统一进同一套原生 UI。会话生命周期、模型调用、多轮对话、审批与文件差异全部由本仓库的 Host Runtime + Protocol Core + 原生适配器管理；凭据与权限决定仍属于各原生 Harness。
+
+![Harness Mix 首页](docs/images/harness-mix-home.png)
+
+## 能做什么
+
+- 在 Codex Desktop 原生输入框中选择 Harness 并发起会话。
+- 流式呈现回答、思考、命令执行、工具调用、文件变更和上下文压缩。
+- 调用每个 Harness 原生提供的模型、权限、上下文用量和快捷指令。
+- 会话中原地切换 Harness（`/switch <Harness 名> [备注]` 或 `codexhost/thread/harness/switch`）：会话历史与文件现场保留在 Host 线程上，切换后首轮自动携带一次性上下文信封；切回旧 Harness 时按其原生机制（Pi `--session` / Claude `resume`）恢复原会话。
+- 原生 Diff、审批与提问组件直接渲染，审批路由回原生 Harness，不代替用户作出权限决定。
+- 通过 Adapter 注册新 Harness，UI 侧无需理解厂商协议。
+
+![Harness Mix 会话](docs/images/harness-mix-session.png)
+
+## 原生接入
+
+通过 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` | Web Remote、Typert RPC、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 | `qoder acp`（阿里 Qoder CLI，共享 `acp.js` 工厂） | 会话、流式回答与思考、工具、审批、模型选择 |
+| Workbuddy | `codebuddy acp`（腾讯 Workbuddy / CodeBuddy CLI，共享 `acp.js` 工厂） | 会话、流式回答与思考、工具、审批、模型选择 |
+| ZCode | `zcode acp`（智谱 AI ZCode CLI，共享 `acp.js` 工厂） | 会话、流式回答与思考、工具、审批、GLM 模型识别 |
+| Trae | `traecli acp serve`（字节跳动 Trae CLI Agent，共享 `acp.js` 工厂） | 会话、流式回答与思考、工具、审批、模型选择 |
+
+能力只在 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 --> Workbuddy[Workbuddy ACP stdio]
+  Registry --> ZCode[ZCode ACP stdio]
+  Registry --> Trae[Trae ACP stdio]
+```
+
+```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
+```
+
+### 运行方式
+
+原生模式（默认）：本地编译的 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` 显式指定源码目录，但版本必须被内核支持。
+
+原生接入方式、数据目录和验证说明见 [原生 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)
+- [设计验收记录](design-qa.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,23 @@
+{
+  "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."
+    }
+  ]
+}

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/harness-management.md

@@ -0,0 +1,41 @@
+# Harness 管理
+
+入口：右上角「Harness 管理」、左下角设置，或 `Ctrl+,`。
+
+## 连接
+
+分别检查 Codex、Claude Code、Pi、DeepSeek Harness 的本机安装状态，显示原生接口、诊断信息和检查耗时。检测不会发送用户消息。程序可用不等于账号已登录。
+
+## 账号
+
+| Harness | 读取状态 | 管理方式 |
+| --- | --- | --- |
+| Codex | 原生 `account/read` | 原生 `account/login/start` 打开浏览器；支持取消、完成通知与退出登录 |
+| Claude Code | 原生 `claude auth status --json` | 打开原生认证窗口执行 `claude auth login/logout`，完成后刷新 |
+| Pi | 原生 RPC 模型目录中的供应商 | 打开 Pi 原生交互终端，使用 `/login` 与 `/logout` |
+| DeepSeek Harness | 原生 Web Remote 模型目录中的供应商 | 在独立、安全隔离的应用窗口中打开 DSH 原生管理页面，进入设置管理供应商 |
+
+Pi / DSH 显示「已配置」而非「已登录」，目录存在不能证明凭据通过在线验证。登录与配置仍使用原生程序自己的账号存储，Harness Mix 不复制账号密钥。当前使用各原生程序的本机账号环境，不提供独立多账号池。
+
+修改登录前会检查该 Harness 是否有运行中的任务。Codex 登录连接保留至完成、取消或五分钟超时；关闭设置不会取消浏览器登录，应用退出会取消待完成的登录。
+
+## 模型
+
+- 按 Harness 读取原生模型目录，支持按名称和供应商筛选。
+- 「保存为新对话默认」写入 Harness Mix 的本地非敏感偏好，刷新与重启后保留，不改写原生模型配置。
+- 同名模型按供应商区分。默认选择只允许来自该 Harness 实际返回的目录。
+- 「应用到当前对话」通过现有原生 `setModel` 链路执行；任务运行中不能切换。
+- 选择「跟随原生默认」可清除 Harness Mix 的默认模型覆盖。
+- 配置或登录完成后刷新状态和目录，使新的供应商与模型可见。
+
+## 验证
+
+```powershell
+npm run test:native-ui
+npm run smoke:native-ui
+npm run e2e:native
+```
+
+`test:native-ui` 覆盖账号字段白名单、模型供应商身份、并发默认值保存、登录连接生命周期和设置页渲染逻辑。`smoke:native-ui` 使用 Electron 与模拟原生响应，检查 Renderer 注入及设置界面的关键交互。
+
+`e2e:native` 是只读协议验收：读取可用 Harness 与模型目录，不执行登录/退出或修改凭据。完整账号管理和 DSH 原生页面重开仍需在真实 Codex Desktop 重启验收中人工确认，不能由这条命令代替。

package/docs/multi-agent-collaboration.md

@@ -0,0 +1,89 @@
+# 多 Agent 协作
+
+## 用法
+
+重新启动 Harness Mix 后，新建或恢复一个 Pi / Oh My Pi / Claude Code / **Codex（协作）** / Grok / OpenCode 任务，输入 `@`，在 **Agents** 页选择目标 Harness；**会话** 页单独提供历史引用。左右键切换分页，上下键选择，Enter/Tab 插入。Codex（协作）通过 Host Adapter 使用原生 app-server；原来的 Codex 入口仍为官方直通。可用目标来自 Host 注册的 Adapter；未就绪的目标不可选。示例：
+
+```text
+你负责实现后端。
+@claude-code 审查 API 设计，只读，不修改文件。
+@pi 为 tests/ 编写测试，不修改 src/。
+收齐结果后由你运行验证并总结。
+```
+
+也可直接输入 `@pi`、`@claude`、`@dsh`、`@codex` 等已注册 ID/别名。显式 `[名称](harness-mix://agent/pi)` 引用可随草稿复制；代码块、行内代码和邮箱里的 @ 不作为路由元数据。提及本身由主模型结合用户任务理解，Host 不按文字片段盲目拆任务。
+
+## 执行方式
+
+借鉴 Codeg 的 [委派工具](https://github.com/xintaofei/codeg/blob/main/src-tauri/src/acp/delegation/tool_schema.json) 和 [Agent 引用路由](https://github.com/xintaofei/codeg/blob/main/src-tauri/src/acp/agent_mentions.rs)：
+
+1. Host 为主任务提供会话绑定的协作工具。Claude 通过 SDK 的 MCP 配置，Codex Adapter 通过 app-server 的线程 MCP 配置，Pi/OMP 通过原生扩展加载，Grok 通过原生 `session/new` 的 `mcpServers` 槽注入（L1），OpenCode 通过 `OPENCODE_CONFIG_CONTENT` 内联配置注入 `mcp.servers`（L2，运行时最高优先级、不写任何用户配置文件）。
+2. 主模型调用 `delegate_to_agent(agent_type, task)`，立即取得 `task_id`，可以继续发起其他任务。
+3. Host 创建带 `parentThreadId` 的独立原生会话。任务中需要的上下文由主模型明确传递，不复制其他 Harness 的隐藏状态、账户或权限。
+4. `update_agent_plan(steps)` 发布开发、审查、返工和最终验收计划；步骤状态为 pending / in_progress / completed。`get_delegation_status(task_ids, wait_ms)` 收取状态和最终文本；单次等待不超过 60 秒。`message_agent` 在已结束的子会话中继续对话，`cancel_delegation` 取消子任务。
+5. 结果作为真正的原生工具结果返回主模型，由主模型验证、整合并继续执行。Host 额外投影原生 `collabAgentToolCall` 协作卡片（真实子任务 ID、Harness 名称、提示词和最终状态），不代替主模型生成总结。
+
+`list_agents` 提供真实可用性。旧 `/delegate` 仍是独立的手动委派入口，其完成结果只回投父任务工具卡片，不自动调用父模型。
+
+## 执行边界
+
+- 同一主任务最多四个同时运行的子任务，每轮最多创建十六个；子任务不注入协作工具，不允许递归委派。
+- 模型工具委派默认共享主任务目录，子 Agent 使用独立原生会话。开发完成后再委派审查，审查意见通过 `message_agent` 发回原开发者，修复后复用原审查会话复审。主任务应等待依赖步骤完成并避免同时修改相同文件。主任务负责共享目录整体文件快照。显式 `isolation=worktree`（或 Git 项目中的 `auto`）仍创建隔离分支与工作区，保存主目录当前非忽略文件作为起点，保留用户暂存区；隔离改动不会自动出现在主目录。
+- 协作不创建独立面板或第二套 UI。父子关系通过原生 `parentThreadId` 投影，子任务进入 Codex 原生任务体系；委派和跟进显示为原生协作卡片；普通工具及轮询仍显示为 MCP 工具卡片，审批在相应原生子任务中处理，文件变化由原生 Changes 界面展示。
+- 主任务可调用 `review_delegation_changes` 在原生工具卡片中审查 worktree patch。只有用户明确要求应用时才可调用 `apply_delegation_changes`，并必须提交刚审查得到的 digest。应用前检查 Git patch 冲突；冲突时保留两个目录，交给用户处理。worktree 保留供检查，不自动删除。隔离子任务有独立审查快照；共享子任务仍由主任务记录整体快照。旧 `/delegate` 手动入口仍为共享目录。
+- 同目录的无关任务仍受原有执行互斥约束。父任务结束/取消、Host 关闭会取消尚未完成的子任务；30 分钟未完成的子任务会超时。
+- 协作 HTTP 桥仅绑定 loopback，以每个主任务的随机本地能力标识鉴权；工具参数校验，子任务归属检查，外部 Origin 拒绝。该标识不是模型账户令牌。Host 不读取或代理原生账户密钥。
+- Claude 的 `canUseTool` 和 Codex MCP elicitation 继续走原生审批。需要确认时，用户在相应任务的审批界面处理；自动验证不会代答。
+- 主任务 Fork 会重新绑定自己的协作身份，不复用源任务的子任务访问权。
+- task_id、父子会话、任务文本、结果和 worktree 起点在独立串行存储中持久化；重启后在途任务变为 interrupted，不自动重复执行有副作用的操作。点击「继续协作」向原主任务发送续跑请求，主模型用 `list_delegations` / `resume_delegation` 恢复原子会话。原生会话丢失或无法恢复会明确报错。会话鉴权标识不持久化，重启重新签发。
+
+## 支持与验证范围
+
+| 入口 | 状态 |
+| --- | --- |
+| Pi 主任务 | 原生扩展工具；Pi→Pi、Pi→Claude 两条真实模型链路通过 |
+| Claude Code 主任务 | SDK MCP 注入；本机真实运行触发原生工具审批，未代答，尚未完成模型闭环验收 |
+| Oh My Pi 主任务 | 同 Pi 家族的扩展接线；本机未安装 OMP，真实验收未完成 |
+| Codex（协作）主任务 | 已接入选择器、模型/强度、恢复归属、@ 菜单；桌面使用配套 CLI。真实请求已到原生 MCP 审批，尚未完成需授权的闭环 |
+| Grok 主任务 | L1：`session/new`/`session/load` 原生 `mcpServers` 槽注入，恢复会话同样携带；真实模型闭环验收待跑 |
+| OpenCode 主任务 | L2：`OPENCODE_CONFIG_CONTENT` 内联配置注入 `mcp.servers`（V2 schema），会话结束即失效；真实模型闭环验收待跑 |
+| DSH 主任务 | 调研结论：DSH 自带 `@deepseek-ai/dsh-mcp-client`（stdio 配置：`transport/serverName/command/args/env`），门存在；host.call 会话通道的 MCP 注入点待上游确认，确认前保持 target-only |
+| 官方 Codex 桌面直通任务 | 保持官方直通，不展示 Host 的 @ 协作菜单；不要把 Adapter 接线等同于已支持这个入口 |
+| 其他 Harness 主任务（含 Antigravity） | Agents 页明确提示需要切换可编排的主 Agent，目标不可选；历史引用仍可用；可使用旧 /delegate |
+| 子任务目标 | 所有已注册且本机可用的 Adapter；不代表每一对组合都已实测 |
+
+```powershell
+npm run test:collaboration
+npm run test:collaboration-recovery
+npm run smoke:collaboration-ui
+npm run e2e:collaboration -- --lead=pi --worker=claude
+npm run check
+npm run test:core-all
+npm run test:native-protocol
+npm run e2e:native
+npm run build:native
+```
+
+`test:collaboration` 使用真实 MCP stdio 子进程、本地鉴权桥和受控原生会话 Adapter 验证并发、结果、跟进、取消、跨任务访问限制、历史引用提示和共享快照策略。UI smoke 只检查原生输入框内的 Harness/历史会话选择、图标、标识、键盘选取和清理，截图位于 `output/collaboration-ui/mentions.png`。协作过程由 Native Protocol 的原生工具卡片测试覆盖。这不是完整 Codex Desktop 的交互验收；构建过程不会重启当前桌面。
+
+2026-09-10 验证：Pi→Claude 两个真实子任务分别在不同 worktree 运行，结果返回主模型并汇总通过。恢复测试覆盖持久化身份、原子会话续跑、不重复建任务；Git 测试覆盖脏目录起点、暂存区保留、过期预览拒绝、冲突时不部分应用。Native Protocol 覆盖父子任务归属与原生 MCP 工具卡片，Electron 仅覆盖原生输入框中的协作引用增强。
+
+## 统一历史
+
+设置 → 会话导入 → 全部历史，支持按标题、目录和会话 ID 搜索、分页、导入并打开。Pi、Claude、Codex 从本机原生历史发现会话；其余 Harness 当前聚合 Host 已管理的历史，并在来源名称上标为「Host 历史」，尚未接入各自 CLI 的外部会话扫描。
+
+导入只创建投影和原生会话引用，不启动模型；再次发送时原生恢复。重复导入返回同一任务。输入 `@` 可从「会话」页选择一条记录；Host 最多读取三条引用，每条只附加最近十二条用户/助手文本，并明确标记为不可执行的历史数据。引用不会创建、恢复或占用原生会话。原始完整工具、隐藏状态和分支数据仍留在原生存储，因此这不是原生历史的无损迁移。原生运行状态未知时，应先关闭其他客户端的同一会话。
+
+## 2026-09-11 Codeg 协作流程修复
+
+- Agents 与历史会话分栏，修复原生 @ 大菜单与协作菜单同时弹出；提示不可用主 Agent 的能力边界。
+- 默认共享目录，使开发与审查读取同一份实际文件；保留显式隔离工作区。多任务等待在任一结果可收取时返回。
+- 新增可更新的原生计划，子任务卡片投影真实会话 ID 与 Harness 名称，跟进复用原会话。
+- 实测 Pi 主任务 + 两个独立 Pi 原生子会话：开发者写入错误样本 41 → 审查者 REVIEW_FAIL → message_agent 交回原开发者修为 42 → 原审查者 REVIEW_PASS → 主模型完成计划并汇总。测试验证文件实际导出值以及两个会话均收到跟进。日志：`output/collaboration-cycle.log`。
+- Pi → Claude 写文件测试到达原生审批，未代答，跨 Harness 写文件闭环尚未通过；不能据此声称全部 Harness 组合已验收。
+
+```powershell
+npm run e2e:collaboration -- --lead=pi --worker=pi --cycle
+```
+
+桌面实测：Pi 主 Agent 切换、Agents/会话切页、Claude 提及精确插入（无重复 @）、图标标识、Antigravity 未支持主编排的提示和草稿清理通过。截图与报告在 `output/collaboration-ui/desktop-*.png` 和 `desktop-report.json`。专用子任务卡片的协议投影已验证；尚未完成真实桌面卡片点击跳转验收。