Repository navigation
v1.8.0-rc.8 — DeepSeek Harness 0.2.2-rc.3 Compatibility
Pre-releasecodex-dsh-native-team v1.8.0-rc.8
Pre-release — released 2026-11-16
External GPT leadership for native DeepSeek Harness Agent Teams — powered by an MCP bridge.
Keep the native team. Replace the reasoning Lead.
This is the second public release of the project and a release candidate
(1.8.0-rc.8), not a stable 1.0. It adds compatibility with DeepSeek Harness
Desktop / Host 0.2.2-rc.3 and a safer offline maintenance upgrade path. Read
the current limitations before installing.
Compatibility warning.
1.8.0-rc.7and earlier adapters do not work on
DSH0.2.2-rc.3: the runtime removed the legacyctx.agentTeamsAPI they
depended on, so the old adapter fails at initialization with
TEAM_API_UNSUPPORTED. Use1.8.0-rc.8with0.2.2-rc.3.
What this project is
codex-dsh-native-team (the DSH MCP Bridge) is an MCP server — registered as
deepseek_harness — that lets an external GPT agent, primarily OpenAI Codex,
act as the only reasoning Lead of a native DeepSeek Harness Agent Team.
The bridge exposes exactly three MCP tools (dsh_delegate_task, dsh_team,
dsh_team_wait) and routes every operation to the official DSH native Team and
Subagent services. DSH keeps its native Root Session, workers, teams, shared task
board, messaging and lifecycle. The DSH Root performs zero model inference:
planning, decisions, coordination and final integration are done by the external
GPT. Workers run in their own native DSH environments with real tools, Skills
and peer communication, and can escalate genuine blockers to the external Lead.
Single-worker and multi-worker delegations both use a real native team.
"Replace the reasoning Lead" means the external GPT takes over the Lead's
decision duties; the DSH Root Session and the official Native Team internals are
kept, not deleted or reimplemented.
Architecture
External GPT / Codex Lead
│ MCP (stdio), 3 tools
▼
MCP Bridge (deepseek_harness)
│ official DSH native Subagent + Team services (0.2.2-rc.3)
▼
DSH Native Team Root (0 model inference)
│
▼
Native DSH Workers ── native tools, global Skills, peer messaging
│
└── task completion / blockers / events ──► wait wakes the external Lead
- The DSH Root Session is real and official, created through
agents.create
and bound withWorkspace.attachSession; root model requests are forbidden by
guards. - Workers keep the official parent/child relations and use the official
list_agents/send_message/wait_agenttools. - The external Lead waits for events instead of polling, decides, and performs
final integration on the exact accepted task revisions.
See the architecture documentation
for the full component and protocol description.
Main changes in 1.8.0-rc.8
Compatibility — official Native Subagent API
DSH 0.2.2-rc.3 removed the legacy ctx.agentTeams methods
(membership, tryMembership, listMembers, spawnTeammate, sendMessage,
waitForChange, interrupt) that 1.8.0-rc.7 required. The RC.8 adapter is
migrated to the official Native Subagent API of 0.2.2-rc.3:
- root/member identity through
subagents.rootOf, membership through
subagents.listDescendants; - Worker creation through
subagents.startActivation(providerspawn,
deliverycaller), using the returned child Session ID as the Worker identity; - messaging through
subagents.sendMessage, interruption through
subagents.interrupt; - the adapter keeps its own event-driven
WaitCoordinator— it is not replaced
by the nativewait_agenttool, and no polling loop was added.
The three MCP tools, the external-GPT-only Lead, the inert DSH Root, the shared
native task board, blocker escalation and the 25-minute default wait are
unchanged.
Team Mode is explicit and persisted
New roots are switched into native Team Mode explicitly (team/mode set to
enabled) and the bridge waits for the official session-persistence flush barrier
before reporting team creation as complete. Historical roots without an explicit
mode are treated as enabled by the official projection and are not silently
mutated; read-only team views expose teamModeEnabled. A closed historical root
is not auto-enabled, and an empty view from a closed team is not treated as
"no tasks".
Worker Session IDs, messaging and task ownership
Native Worker Session IDs are the real identity. Task ownership requests keep
the owner key but carry the Worker Session ID, and the persisted/returned field
remains ownerId. Historical Worker names are kept as read-only external
aliases for existing teams; new Workers cannot reuse an alias, and ambiguous
names require the Session ID.
Native message relay still observes the official agent-message source with the
sender's Session ID and the new body prefix (Agent <name/path/id> sent a message:), while historical Team message from ...: prefixes remain parseable
for replay. Blocking reports are validated against the real sender, current task
ownership and revision, persisted with dedupe and cursor commit before the wait
wakes the Lead, and directed answers pin both the questionId and the Worker
Session ID.
Reliability
- Cold restore now discovers readiness once per root cohort and validates the
whole cohort with one official session list after every root flushes; a
missing root still rejects the whole publication. Production cold restart with
46 historical teams completed in about 49 seconds. - Host/adapter shutdown preserves real disposal errors, keeps the error journal,
waits for persistence and no longer releases the transport or control lock
when close fails. - Control ownership orphaned by the offline maintenance flow is reclaimed only
after the previous process is proven gone. - Completion notifications still come only from a completed current task
revision on the native task board; idle state, settlement or ordinary
messages are not treated as completion.
Safe upgrade
RC.8 adds an operator-driven, fail-closed offline maintenance procedure for
moving an existing installation to a new build on the same 0.2.2-rc.3
runtime:
- an exclusive maintenance window: DSH Desktop/Host must be fully exited through
the official quit path, with an officialsessionPersistence.flush()receipt
and real operating-system exit codes; - kernel single-writer Session leases plus profile/control/storage locks held
during the cutover, so no concurrent writer exists; - a full consistency backup generated and verified at byte level, with the
official readers re-checking sessions, teams, task revisions, event cursors
and acknowledgements before any file is swapped; drift after the backup aborts
the cutover; - program-level forward recovery: recovery restores only the bridge/adapter
program files of the same verified RC.8 build and keeps the latest official
sessions, teams, task revisions, cursors and user configuration. The scenario
was rehearsed during the RC.8 production validation.
There is no automatic rollback, and cross-version downgrade is not
supported. In particular, RC.7 cannot initialize on 0.2.2-rc.3 and is refused
before any write; old business snapshots are audit material and must never be
restored over newer data. The online maintenance entry points remain read-only
preflight/refusal by design.
Verification
- 220/220 automated tests passed, 0 failed, 0 skipped, 0 cancelled
(20 test files, re-run on the public release tree). node scripts/check-architecture.mjs: 24 maintained source modules, 3 MCP
tools, 0 legacy backend dependencies, 0 unreachable modules.- Reproducible adapter build: rebuilding
native-team-plugin/dist/host.mjs
from this release tree produced a byte-identical bundle
(12ca4e5d…) and the same build fingerprint (633ddb…0c34) as the
production-verified adapter. - Real native-team acceptance on DSH Desktop/Host
0.2.2-rc.3on Windows with
real model Workers: single-Worker task, dual-Worker native bidirectional
messaging, a real[codex:blocking]question answered throughquestionId
and resumed to completion, a Global Skill loaded inside a Worker, and the
default wait contract (omittedtimeoutMs→ 1,500,000 ms) with early wakes. - The DSH Root recorded
rootModelRequests: 0across all roots and root events
in acceptance. - Historical data was preserved through the production maintenance window:
45 historical teams and 2,648 original events unchanged, 428 session files and
38 workspaces preserved, and a cold restart kept team/task revisions, cursors
and session files without prompt replay.
Requirements
- Windows (primary and only tested platform; see limitations).
- Node.js >= 24.
- DSH Desktop / Host
0.2.2-rc.3exactly — the officially tested runtime.
RC.8 requires the native Team/Subagent services present in that runtime. - An external MCP-capable client logged in — primarily OpenAI Codex — with
the bridge registered asdeepseek_harness(stdio,node src/server.mjs,
managed tool timeout 3900 s). - An absolute workspace directory the Team will operate in. Installation is
read-only by default; workspace writes require the explicit-Writeopt-in.
Full installation and upgrade instructions:
INSTALLATION.md.
Upgrading from 1.8.0-rc.7
scripts/install.ps1 only performs a fresh install into an empty install
directory. Existing installations must use the documented upgrade flow, not a
fresh install into the old directory:
- Read INSTALLATION.md
and the maintenance prerequisites. - Take a verified backup of the current installation and state before changing
anything. - Perform the exclusive offline maintenance cutover to the RC.8 source and
adapter archive, following the documented preconditions (official exit,
persistence flush receipt, held write leases and locks, verified backup,
fail-closed preflight). - Verify the installed version, the full build fingerprint, the three MCP
tools, the managed MCP registration and Root zero-inference after startup.
If the cutover is blocked, stop and keep the installation as-is; do not force an
online apply. Recovery is a same-version program-level forward repair, never an
automatic rollback to RC.7.
Release assets
| Asset | Description | SHA-256 |
|---|---|---|
dsh-mcp-bridge-1.8.0-rc.8.zip |
Full source and build tree for this release: MCP bridge source, scripts, tests, public docs, the native adapter plugin (source, dist/host.mjs, third-party licenses) and the prebuilt adapter package under packages/. Use it to install the bridge with npm ci --ignore-scripts and to build/install the adapter. |
Listed in SHA256SUMS-1.8.0-rc.8.txt (exact values also in the release description) |
dsh-codex-team-adapter-1.8.0-rc.8.tgz |
Prebuilt native DSH plugin package (dist/host.mjs, dist/THIRD_PARTY_LICENSES.txt, cordis.patch.yml). Installed with scripts/install.ps1 -Workspace <absolute-workspace> -Archive <absolute-path-to-tgz> [-Write] for a fresh install. |
Listed in SHA256SUMS-1.8.0-rc.8.txt (exact values also in the release description) |
SHA256SUMS-1.8.0-rc.8.txt |
SHA-256 checksums for the two assets above. | — |
Verify the downloaded files before installing:
Get-FileHash .\dsh-mcp-bridge-1.8.0-rc.8.zip -Algorithm SHA256
Get-FileHash .\dsh-codex-team-adapter-1.8.0-rc.8.tgz -Algorithm SHA256The digests must match the values published in SHA256SUMS-1.8.0-rc.8.txt and in
the release description. GitHub's automatically generated "Source code (zip)"
and "Source code (tar.gz)" archives contain the repository at the
v1.8.0-rc.8 tag; the ZIP release asset additionally contains the prebuilt
adapter package under packages/.
Exact checksums
| Asset | Bytes | SHA-256 |
|---|---|---|
dsh-mcp-bridge-1.8.0-rc.8.zip |
616672 | 066e6316952d5fe78b5b67e1b453489cbb588eb074ab7a9dc4cc4e35bf74155d |
dsh-codex-team-adapter-1.8.0-rc.8.tgz |
76409 | 4ebbc8ac9cefabf9ea3dcc17947b2c46fec7a311a3cf0fed63257f77e7aa4d2f |
SHA256SUMS-1.8.0-rc.8.txt |
200 | 40bb6b1faf4f57bddf0fe19430e06b4d3908c5fc5089d3aa9b6089b24b224da4 |
Release commit: f6abc16cab4f2d3263787c55ad891d2aac3552f3 (tag v1.8.0-rc.8).
Quick start
# 1. Install the bridge (from an unpacked release ZIP)
npm ci --ignore-scripts
npm test
# 2. Install the native adapter into a DSH workspace (fresh install, read-only by default)
.\scripts\install.ps1 -Workspace C:\path\to\your\workspace `
-Archive C:\path\to\dsh-codex-team-adapter-1.8.0-rc.8.tgz
# 3. Probe the native Host from the bridge directory
node src\cli.mjs doctorThe installer registers the bridge as the managed stdio MCP server
deepseek_harness in your client config automatically (it writes the managed
~/.codex/config.toml block; never commit your real client config). Start a new
client session, or reconnect the MCP connection, so the v1.8.0-rc.8 tool schema
loads. A first delegation can be as short as:
{"requestId": "work-1", "prompt": "Implement and verify ...", "permission": "workspace-write"}More examples, the multi-worker flow and troubleshooting are in the
README
and INSTALLATION.md.
Current limitations
- Release candidate quality — not a stable
1.0; APIs and behavior may
change between release candidates. - Compatibility is only what was tested: DSH Desktop/Host
0.2.2-rc.3,
Node.js >= 24, Windows. No claim of universal compatibility with other DSH or
Codex versions or with macOS/Linux. - No automatic rollback and no supported cross-version downgrade. RC.7
cannot run on0.2.2-rc.3. Recovery is same-version program-level forward
repair only, and old data snapshots must not be restored over newer data. - The real 25-minute wall-clock timeout expiry was not waited for during
acceptance; the default contract and early completion/blocker wakes were
verified. - Human-eyes UI screenshots were not re-captured for this release; the existing
screenshots are kept from the previous release and are not claimed as new RC.8
evidence. - The HMR full chain was not re-validated in the production acceptance window.
- Host-startup-failure injection was not performed; the recovery drill covered
removing the installed program entry and re-applying the same RC.8 build. - The outer Codex client/wrapper may still incur its own model-continuation cost
during long waits. The DSH Root doing zero inference does not mean total
token cost is zero: workers and the external GPT still consume tokens. No
token-reduction claim is made. - Auto-archive after 90 days is supported; automatic delete is not
implemented, and DSH official Session delete is not supported. Archive and
delete are different features. - Workers sharing one workspace:
writeScopesare collaboration hints, not file
locks; Auto Review is not an OS sandbox. Use separate git worktrees if
isolation is needed. - An existing Codex Desktop stdio MCP connection may cache the previous tool
schema until it reconnects or starts a new session.
Documentation and feedback
- README
- Architecture
- Installation
- Contributing
- Security policy
- Bug reports and feature requests:
https://github.com/asdstrind/codex-dsh-native-team/issues - Repository: https://github.com/asdstrind/codex-dsh-native-team
License
The project's own code is released under the
MIT License
(Copyright (c) 2026 asdstrind). Third-party components and bundled
dependencies are listed in
THIRD_PARTY_NOTICES.md.
This is an independent third-party open-source project. It is not a
DeepSeek official product and is not endorsed by DeepSeek. DeepSeek Harness
(DSH) is an MIT-licensed product/platform by DeepSeek; this project plugs into
it and does not redistribute DSH.
中文摘要
codex-dsh-native-team v1.8.0-rc.8(预发布版) 是一个 MCP 桥接服务(注册名
deepseek_harness),让外部 GPT(主要是 OpenAI Codex)成为原生 DeepSeek
Harness Agent Team 中唯一负责推理的 Lead。项目只暴露三个 MCP 工具
(dsh_delegate_task、dsh_team、dsh_team_wait),所有操作都走 DSH 官方原生
Team / Subagent 服务:DSH 保留原生 Root Session、Worker、共享任务板、消息与生命
周期,Root 自身不做任何模型推理(实测 rootModelRequests: 0),规划、决策与
最终集成都由外部 GPT 完成。
与 DSH 0.2.2-rc.3 的兼容性是本版最重要变化。 0.2.2-rc.3 移除了旧的
ctx.agentTeams 接口,因此 1.8.0-rc.7 及更早的 Adapter 在 0.2.2-rc.3 上会以
TEAM_API_UNSUPPORTED 初始化失败。RC.8 迁移到官方 Native Subagent API
(rootOf / listDescendants / startActivation / sendMessage / interrupt),
在保留原生 Team 模型的前提下恢复兼容。
RC.8 主要变化
- 官方 Native Subagent API 迁移:Worker 以原生 Session ID 为真实身份;任务
所有权请求的owner值改为 Session ID,持久化字段仍为ownerId;历史 Worker
显示名保留为只读外部别名。 - Team Mode 显式启用并持久化:新 Root 显式开启 Team Mode,并在官方
sessions.flush持久化屏障完成后才报告创建完成;历史 Root 由官方投影处理,
只读视图暴露teamModeEnabled。 - 消息与阻塞链路:原生 relay 保留
agent-message与发送方 Session ID,
正文前缀更新并兼容历史前缀;阻塞消息校验真实发送者/任务所有权/Revision 后
持久化去重并唤醒 Lead,定向答复同时固定questionId与 Worker Session ID。 - 可靠性:冷恢复按 Root 批次发现就绪并用一次官方 Session 列表校验整批;
close 失败保留真实错误且不释放控制权;离线维护后仅在旧进程确认退出后回收
控制所有权;生产冷重启(46 个历史 Team)约 49 秒。 - 安全离线升级:新增排他离线维护流程(官方退出路径 + 持久化 flush 回执 +
真实退出码 + 内核单写 Session 租约 + 完整一致性备份校验),并提供同版本
程序级前向恢复。没有自动回滚,不支持跨版本降级,RC.7 在0.2.2-rc.3
上不可用。
验证:自动化回归 220/220;24 个源码模块、3 个 MCP 工具、0 个旧后端依赖;
从公开源码重建的 Adapter 与生产验证构建逐字节一致(指纹 633ddb…0c34);真实
单 Worker、双 Worker 原生双向通信、阻塞问答、Global Skill 加载、Root 零推理与
冷重启验收通过;45 个历史 Team、2648 条事件与 428 个 Session 文件保持完整。
要求与限制:Windows(唯一实测平台)、Node.js >= 24、DSH Desktop/Host
0.2.2-rc.3。本版本为 RC 预发布,不承诺其他 DSH/Codex 版本或 macOS/Linux
兼容;不支持自动回滚或跨版本降级;Root 零推理不代表总体 Token 成本为零;未实测
真实 25 分钟超时到期;未重新采集 RC.8 的 UI 截图;HMR 全链路未重新验证;
90 天自动归档保留,自动删除未实现。完整限制见
Current limitations。
发布物:dsh-mcp-bridge-1.8.0-rc.8.zip(完整源码与构建树,含 packages/
下的适配器 tgz)、dsh-codex-team-adapter-1.8.0-rc.8.tgz(原生 DSH 插件包)及
SHA256SUMS-1.8.0-rc.8.txt。安装前请校验 SHA-256(见上方资产表)。
本项目为独立第三方开源项目,不是 DeepSeek 官方产品,也未获 DeepSeek
背书;项目自身代码采用 MIT 许可证(Copyright (c) 2026 asdstrind)。反馈与问题请
使用 GitHub Issues。