DeepSeek Harness Plus 0.1.0

DeepSeek Harness Plus 0.1.0

中文

DeepSeek Harness Plus 0.1.0 是 Plus 的首个公开版本。它交付了两条核心用户价值：修复子 agent 没有继承当前模型选择的问题，并提供一个面向本地用户的一次性安装引导和系统托盘管理器。首发版本同时建立了 Plus 的变更记录与评审机制，让用户能够区分已经交付、正在实验和仍在规划的能力。

谁适合使用

0.1.0 适合以下用户：

• 在 Harness Web 中切换模型，并使用子 agent 分解任务。
• 希望在 Linux 或 Windows 上通过图形化引导建立本地 Harness runtime。
• 希望安装完成后从系统托盘启动、停止、打开、升级或修复本地服务。
• 需要一个明确记录社区修复、兼容性和验证证据的 Harness 分支。

完整功能变化

1. 子 agent 继承当前 UI 模型选择

0.1.0 修复了一个影响实际任务执行的问题：用户在 Harness Web 中选择了模型后，新建的子 agent 可能仍然使用全局默认模型或其他旧配置。

修复后的体验：

• 父 session 当前生效的 provider 和 model 会成为新子 agent 的默认选择。
• 用户在 Web UI 中最新选择的模型优先于全局默认模型。
• 子 agent 仍然可以在确有需要时使用自己的显式模型覆盖。
• provider、model 和相关模型限制会沿子 agent 创建链路传递，不只复制一个显示名称。

这使父 agent 与子 agent 在默认情况下使用用户当前明确选择的模型，避免同一项任务在主会话和子任务之间出现难以察觉的模型差异。

涉及的主要模块：

• @deepseek-ai/dsh-host-apiproxy：提供父 session 当前模型选择。
• @deepseek-ai/dsh-subagent：创建 child agent 时继承父 session 的选择。
• @deepseek-ai/dsh-agent：携带创建 child agent 所需的模型选择信息。

该修复没有修改 agent loop，也没有改变 session durable format。

2. 一次性桌面安装引导

首次运行桌面应用且本地 runtime 尚未建立时，0.1.0 会打开安装引导。用户不需要手动完成 clone、配置文件创建、构建和浏览器启动等分散步骤。

安装引导收集：

• 一个空的安装目录。
• 本地 Harness Web 端口。
• 初始 DeepSeek API key。
• 默认模型。
• 可选的 reasoning effort。

随后桌面应用会：

1. 检查本机是否具备 Git 和 pnpm。
2. 克隆独立的 DeepSeek Harness Plus checkout。
3. 为该安装创建隔离的 DSH_HOME。
4. 写入首次启动所需的 credential、默认模型和 reasoning 设置。
5. 安装锁文件指定的依赖并构建源码。
6. 启动本地 Harness Web。
7. 在默认浏览器中打开 Harness Web。
8. 关闭一次性安装引导，后续日常工作回到 Web 页面。

桌面引导只负责建立第一个可运行环境，不会变成第二个长期设置中心。安装完成后，模型、credential、workspace、preset 和 agent 操作继续由 Harness Web 管理。

3. 安装失败后的 Repair 路径

首次安装不是一个“全部成功才留下任何状态”的黑盒操作。0.1.0 在 checkout 克隆成功后就保存 runtime 记录，因此后续依赖安装或构建失败时，用户仍然可以从托盘进入 Repair，而不是面对一个既无法继续、也无法恢复的半成品目录。

Repair installation 会：

• 使用锁文件恢复依赖。
• 重新构建当前 checkout。
• 保留用户已经选择的安装路径和本地 runtime 记录。

缺少 Git、pnpm 或构建命令失败时，安装引导会显示失败信息，不会声称安装已经完成。

4. 系统托盘管理本地 Harness runtime

安装完成后，桌面应用驻留在系统托盘，为本地 runtime 提供日常生命周期操作。

托盘操作包括：

• Open DeepSeek Harness：在默认浏览器打开已配置的本地 Web 地址。
• Start service：启动本地 Harness Web，并等待服务开始监听。
• Stop service：停止本地 Web 进程，同时保留 settings、workspace 和 session 数据。
• Upgrade Plus：快进更新 checkout、恢复锁定依赖、重新构建；如果升级前 runtime 正在运行，升级完成后重新启动。
• Repair installation：恢复依赖并重新构建当前安装。
• Open local data folder：打开当前 Plus 安装的本地数据目录。

托盘会区分用户主动停止和进程意外退出，避免把一次正常 Stop 显示为 runtime 崩溃。

5. 独立的本地安装与数据目录

桌面版不会复用任意现有源码目录或全局配置作为隐式安装目标。0.1.0 为桌面安装建立独立 checkout 和隔离 DSH_HOME：

• 安装源码与用户的其他 Harness checkout 分开。
• 首次 credential 和 model 设置写入该 runtime 自己的数据目录。
• 停止、升级或修复桌面 runtime 不会要求用户手动切换终端工作目录。
• 安装后的日常配置仍在 Harness Web 中完成。

6. Linux 与 Windows 首发安装包

0.1.0 建立了 DeepSeek Harness Plus 的第一套公开桌面发行链路：

• Linux x64 AppImage。
• Debian / Ubuntu x64 deb package。
• Windows NSIS installer。

Linux 和 Windows 产物分别在对应 GitHub runner 上构建并上传。Release 发布前对 draft 中的文件名、大小和可下载性进行了检查。

macOS 没有随 0.1.0 发布。虽然源码中存在 DMG target，但普通用户可用的公开 macOS 安装包需要 Developer ID 签名和 notarization；首发版本选择明确延期，而不是发布一个系统默认会阻止打开的 unsigned DMG。

7. Plus 变更记录与兼容性说明

0.1.0 建立了 Plus 相对上游差异的可审阅记录。用户和维护者可以查看一项改动为什么存在、影响哪些文件、与上游哪个 revision 对比，以及如何验证。

记录分为：

• diffs/core/registry.yaml：上游 Harness 核心和核心 plugin 的行为差异。
• diffs/community/registry.yaml：桌面、治理、社区扩展和部署相关差异。
• presets/compositions/registry.yaml：未来 plugin 和 preset 的组合声明与冲突检查。

0.1.0 的核心 active 记录是 child agent 继承父 session 当前 UI 模型选择。桌面安装器在首发开发阶段作为 community 记录维护，公开产物在 Release 审核后发布。

8. Plus PR 治理与初学者可读说明

首发版本增加了面向人类和 AI contributor 的统一 PR 证据结构。每个 Plus PR 需要说明：

• 用户问题和产品结果。
• 架构与 owner。
• 实现范围。
• 代码审查结论。
• 测试治理。
• 验证证据。
• 影响的 core/community diff records。

GitHub governance workflow 会检查必需段落、diff registry 和 composition claims。AI 生成的证据用于帮助审阅，不会替代人类 maintainer 的最终决定。

同时新增 beginner-friendly PR authoring skill，要求 PR 先解释用户能做什么、证据是什么、哪些内容没有交付，再介绍内部实现，避免把 PR 写成只有作者看得懂的开发日志。

首次安装后的用户流程

1. 下载并启动对应平台安装包。
2. 在首次引导中选择空安装目录和本地端口。
3. 输入初始 DeepSeek API key、默认模型和可选 reasoning effort。
4. 等待 clone、依赖安装和构建完成。
5. 浏览器自动打开 Harness Web。
6. 后续在 Harness Web 中管理模型、credential、workspace 和 agent。
7. 使用系统托盘启动、停止、打开、升级或修复本地 runtime。

下载与校验

平台	文件	大小	SHA-256
Linux AppImage	deepseek-harness-plus-0.1.0.AppImage	115,419,137 bytes	066a0a8c39cf3cd2097eda7ebd831de045c3b5f5730ae9e18f039ecfa0addfe5
Debian / Ubuntu	deepseek-harness-plus-0.1.0.deb	90,358,092 bytes	278ee819db6e109454a3b9107af9a4d5d8e4d0191847077c604ed93383488a03
Windows	DeepSeek.Harness.Plus.Setup.0.1.0.exe	93,610,129 bytes	8c072b2485d410eabb657b47233b91918914ce571d112ddd869e7af1e6c70929

平台要求与使用限制

• 桌面安装流程需要本机具备 Git 和 pnpm，因为 0.1.0 使用源码 checkout 建立本地 runtime。
• 公开安装包只覆盖 Linux x64 和 Windows；没有 macOS 安装包。
• 桌面 helper 负责本地服务生命周期，不负责替代 Harness Web 的日常设置页面。
• 当前 runtime 适合本地私有使用，不包含多用户或公网部署能力。
• 0.1.0 没有提供可安装 preset catalog。
• 安装包在匹配平台的 GitHub runner 上完成构建；当时尚未建立桌面能力的完整端到端 UI 自动化套件。

本版本不包含

以下路线图能力在 0.1.0 中仍未交付：

• 代码开发 preset。
• 智能问数 preset。
• 多用户 runtime preset。
• AIGC preset。
• 社区运营 preset。
• macOS 签名、notarization 和公开安装包。
• 0.2.0 后续加入的 Settings 系统默认应用 opener。
• 0.2.0 后续加入的当前模型 Web Search。
• 0.2.0 后续加入的独立 Supervisor 进度页和重启恢复流程。

验证证据

• Child agent 模型继承拥有 Host API 和 in-process subagent 聚焦回归覆盖。
• Session-level UI model selection reproduction 验证了父 session 当前选择可以到达 child agent。
• 一次性安装引导完成了 folder、model、confirmation 和 progress 页面检查。
• Daemon lifecycle 验证覆盖 starting、running 和用户主动 stopped 状态。
• Linux 本地打包生成 AppImage 和 deb，并检查 deb metadata。
• GitHub Actions 在 Linux 和 Windows runner 上完成对应平台打包并上传 artifacts。
• Plus governance verifier 和文档 doc-sync 28 项门禁通过。
• Release 发布前记录并核对了三个资产的 SHA-256。

关联改动

• PR #1 — First Plus foundations: reliable child models and a local desktop helper
• PR #2 — Point readers to the public Plus 0.1.0 release

完整首发代码固定在 tag plus-v0.1.0。

---

English

DeepSeek Harness Plus 0.1.0 is the first public release of Plus. It delivers two core user benefits: it fixes the issue where subagents did not inherit the current model selection, and it provides a one-time installation wizard and system tray manager for local users. This initial release also establishes Plus's changelog and review process, allowing users to distinguish between capabilities that have been delivered, are being experimented with, and are still planned.

Who Should Use It

0.1.0 is for users who:

• Switch models in Harness Web and use subagents to break down tasks.
• Want to set up a local Harness runtime through a graphical wizard on Linux or Windows.
• Want to start, stop, open, upgrade, or repair local services from the system tray after installation.
• Need a Harness fork that clearly records community fixes, compatibility, and validation evidence.

Complete Feature Changes

1. Subagents Inherit the Current UI Model Selection

0.1.0 fixes an issue affecting real task execution: after a user selected a model in Harness Web, newly created subagents could still use the global default model or another old configuration.

The experience after the fix:

• The provider and model currently in effect for the parent session become the default selection for new subagents.
• The model most recently selected by the user in the Web UI takes precedence over the global default model.
• Subagents can still use their own explicit model override when genuinely needed.
• The provider, model, and related model restrictions are passed through the subagent creation path, rather than copying only a display name.

This causes parent agents and subagents to use the model the user has currently selected explicitly by default, avoiding subtle model differences between the main session and subtasks of the same task.

Main modules involved:

• @deepseek-ai/dsh-host-apiproxy: provides the parent session's current model selection.
• @deepseek-ai/dsh-subagent: inherits the parent session's selection when creating a child agent.
• @deepseek-ai/dsh-agent: carries the model-selection information needed to create a child agent.

This fix does not modify the agent loop or change the session durable format.

2. One-Time Desktop Installation Wizard

When the desktop app is run for the first time and a local runtime has not yet been created, 0.1.0 opens the installation wizard. Users do not need to manually complete scattered steps such as cloning, creating configuration files, building, and launching a browser.

The installation wizard collects:

• An empty installation directory.
• A local Harness Web port.
• An initial DeepSeek API key.
• A default model.
• Optional reasoning effort.

The desktop app then:

1. Checks whether Git and pnpm are available on the machine.
2. Clones a dedicated DeepSeek Harness Plus checkout.
3. Creates an isolated DSH_HOME for that installation.
4. Writes the credentials, default model, and reasoning settings required for first launch.
5. Installs the dependencies specified by the lockfile and builds the source.
6. Starts local Harness Web.
7. Opens Harness Web in the default browser.
8. Closes the one-time installation wizard; subsequent daily work returns to the Web page.

The desktop wizard is responsible only for establishing the first runnable environment; it does not become a second long-term settings center. After installation, Harness Web continues to manage models, credentials, workspaces, presets, and agent operations.

3. Repair Path After Installation Failure

The first installation is not a black-box operation that leaves any state only if everything succeeds. 0.1.0 saves the runtime record as soon as checkout cloning succeeds, so if subsequent dependency installation or building fails, users can still enter Repair from the tray instead of facing a half-finished directory that can neither continue nor be recovered.

Repair installation will:

• Restore dependencies using the lockfile.
• Rebuild the current checkout.
• Preserve the installation path and local runtime record already selected by the user.

If Git or pnpm is missing, or the build command fails, the installation wizard displays failure information and does not claim that installation has completed.

4. System Tray Management for the Local Harness Runtime

After installation, the desktop app resides in the system tray and provides day-to-day lifecycle operations for the local runtime.

Tray actions include:

• Open DeepSeek Harness: opens the configured local Web address in the default browser.
• Start service: starts local Harness Web and waits for the service to begin listening.
• Stop service: stops the local Web process while preserving settings, workspace, and session data.
• Upgrade Plus: fast-forwards the checkout, restores locked dependencies, and rebuilds; if the runtime was running before the upgrade, it restarts after the upgrade completes.
• Repair installation: restores dependencies and rebuilds the current installation.
• Open local data folder: opens the local data directory for the current Plus installation.

The tray distinguishes between a user-initiated stop and an unexpected process exit, avoiding showing a normal Stop as a runtime crash.

5. Dedicated Local Installation and Data Directories

The desktop edition does not reuse any existing source directory or global configuration as an implicit installation target. 0.1.0 establishes a dedicated checkout and isolated DSH_HOME for desktop installations:

• Installation source is separate from the user's other Harness checkouts.
• Initial credential and model settings are written to that runtime's own data directory.
• Stopping, upgrading, or repairing the desktop runtime does not require users to manually change terminal working directories.
• Day-to-day configuration after installation is still completed in Harness Web.

6. Initial Linux and Windows Installation Packages

0.1.0 establishes the first public desktop release pipeline for DeepSeek Harness Plus:

• Linux x64 AppImage.
• Debian / Ubuntu x64 deb package.
• Windows NSIS installer.

Linux and Windows artifacts are built and uploaded on their respective GitHub runners. File names, sizes, and download availability in the draft were checked before the Release was published.

macOS was not released with 0.1.0. Although the source includes a DMG target, a public macOS installer for ordinary users requires Developer ID signing and notarization; the initial release explicitly deferred it rather than releasing an unsigned DMG that the system would block from opening by default.

7. Plus Changelog and Compatibility Notes

0.1.0 establishes a reviewable record of Plus's differences from upstream. Users and maintainers can see why a change exists, which files it affects, which upstream revision it is compared with, and how to validate it.

The records are organized into:

• diffs/core/registry.yaml: behavioral differences in the upstream Harness core and core plugins.
• diffs/community/registry.yaml: differences related to desktop, governance, community extensions, and deployment.
• presets/compositions/registry.yaml: composition declarations and conflict checks for future plugins and presets.

The core active record in 0.1.0 is that child agents inherit the parent session's current UI model selection. The desktop installer was maintained as a community record during initial-release development, and public artifacts were published after Release review.

8. Plus PR Governance and Beginner-Readable Documentation

The initial release adds a unified PR evidence structure for human and AI contributors. Every Plus PR must describe:

• The user problem and product outcome.
• The architecture and owner.
• The implementation scope.
• The code review conclusion.
• Test governance.
• Validation evidence.
• Affected core/community diff records.

The GitHub governance workflow checks required sections, the diff registry, and composition claims. AI-generated evidence helps with review; it does not replace the final decision of a human maintainer.

A beginner-friendly PR authoring skill was also added. It requires PRs to first explain what users can do, what the evidence is, and what has not been delivered, before introducing the internal implementation, so that PRs do not become development logs only their authors can understand.

User Workflow After First Installation

1. Download and launch the installation package for the relevant platform.
2. Select an empty installation directory and local port in the first-run wizard.
3. Enter the initial DeepSeek API key, default model, and optional reasoning effort.
4. Wait for cloning, dependency installation, and building to complete.
5. Harness Web opens automatically in the browser.
6. Subsequently manage models, credentials, workspaces, and agents in Harness Web.
7. Use the system tray to start, stop, open, upgrade, or repair the local runtime.

Downloads and Verification

Platform	File	Size	SHA-256
Linux AppImage	deepseek-harness-plus-0.1.0.AppImage	115,419,137 bytes	066a0a8c39cf3cd2097eda7ebd831de045c3b5f5730ae9e18f039ecfa0addfe5
Debian / Ubuntu	deepseek-harness-plus-0.1.0.deb	90,358,092 bytes	278ee819db6e109454a3b9107af9a4d5d8e4d0191847077c604ed93383488a03
Windows	DeepSeek.Harness.Plus.Setup.0.1.0.exe	93,610,129 bytes	8c072b2485d410eabb657b47233b91918914ce571d112ddd869e7af1e6c70929

Platform Requirements and Usage Limitations

• The desktop installation flow requires Git and pnpm on the local machine because 0.1.0 uses a source checkout to establish the local runtime.
• Public installation packages cover only Linux x64 and Windows; there is no macOS installation package.
• The desktop helper is responsible for local service lifecycle management; it does not replace Harness Web's day-to-day settings pages.
• The current runtime is intended for local private use and does not include multi-user or public-network deployment capabilities.
• 0.1.0 does not provide an installable preset catalog.
• The installation packages were built on matching-platform GitHub runners; a complete end-to-end UI automation suite for desktop capabilities had not yet been established at that time.

Not Included in This Release

The following roadmap capabilities had still not been delivered in 0.1.0:

• Code development preset.
• Intelligent data Q&A preset.
• Multi-user runtime preset.
• AIGC preset.
• Community operations preset.
• macOS signing, notarization, and public installation package.
• The Settings system default application opener added later in 0.2.0.
• The current-model Web Search added later in 0.2.0.
• The standalone Supervisor progress page and restart recovery flow added later in 0.2.0.

Validation Evidence

• Child agent model inheritance has focused regression coverage for the Host API and in-process subagents.
• A session-level UI model selection reproduction verified that the parent session's current selection can reach the child agent.
• The one-time installation wizard completed checks for the folder, model, confirmation, and progress pages.
• Daemon lifecycle validation covers the starting, running, and user-initiated stopped states.
• Local Linux packaging generated the AppImage and deb, and deb metadata was checked.
• GitHub Actions completed platform-specific packaging and uploaded artifacts on Linux and Windows runners.
• The Plus governance verifier and the 28 checks in documentation doc-sync passed.
• The SHA-256 values for all three assets were recorded and verified before the Release was published.

Related Changes

• PR #1 — First Plus foundations: reliable child models and a local desktop helper
• PR #2 — Point readers to the public Plus 0.1.0 release

The complete initial-release code is pinned at tag plus-v0.1.0.