Repository navigation
v1.8.0-rc.7 — Native DSH Agent Teams led by an external GPT
Pre-releasecodex-dsh-native-team v1.8.0-rc.7
Pre-release — released 2026-11-12
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 first public open-source release of the project. It is a release
candidate (1.8.0-rc.7), not a stable 1.0: read the
current limitations before installing.
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 DSH's official experimental
Native Agent Team Service and Subagent Runtime. DSH keeps its native Root
Session, workers, teams, 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 Native Agent Team Service + Subagent Runtime
▼
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.7
Global Skills integration
The native Worker preset now mounts the official DSH skill filesystem and
skill-tool components at the same scope as the Worker. New workers see the same
Skill catalog DSH makes available natively (21 native catalog entries were
observed in acceptance), project .dsh/skills and .agents/skills entries take
precedence, same-name overrides and disable-model-invocation are handled by
the official registry, and Skill directory resources can be read read-only
inside the existing permission boundary. Skill recommendations use directory
metadata only and add 0 model calls; Skill bodies are loaded on demand.
Skills installed only under Codex .codex/skills or Codex plugin directories are
not automatically added to the DSH search roots — see
current limitations.
Default 25-minute wait
When timeoutMs is omitted, dsh_team_wait waits up to 25 minutes
(1,500,000 ms). Waits wake early on task revision completion, real blockers,
important authorizations, serious errors, and integratable state; ordinary
progress is buffered and does not produce heartbeats. requested_timeout_ms
(null means omitted), effective_timeout_ms and recommended_next_wait_ms are
distinct fields, and short waits remain available for explicit diagnostics.
Proactive blocker escalation
A Worker that hits a genuine blocker (missing required input, missing
permission/tool dependency, a verification loop that stops converging) reports
it proactively through the existing send_message path with a first line of the
form [codex:blocking id=<stable-key> task=<task-N>]. The bridge persists the
problem per Worker/task/revision, wakes the external Lead through the existing
wait, and the Lead answers with the existing send operation (questionId). No
fourth MCP tool and no parallel communication service was added.
Also in this release
- Normal synchronous waits omit
timeoutMsinstead of using polling-style
short timeouts; short waits are for explicit diagnostics only. - Worker guidance covers Skills, blocker reporting and low-yield verification
loops; the Worker policy grew while the MCP instructions were trimmed. - Risk-based review only: no default reviewer, no mutual approval, no per-file
reviewer. Independent review is used only for security/permission/
data-corruption risk, core algorithm or interface complexity, design
conflicts, or an explicit review request. - Final integration is performed directly by the external Lead;
integration_ready
is reported when all necessary tasks are complete. - Persistent native Team sessions; teams are archived after 90 days of
completed, quiescent and acknowledged state.
Verification
1.8.0-rc.7baseline: 185 automated tests passed, 0 failed;
node scripts/check-architecture.mjsreports 24 maintained source modules,
3 MCP tools and 0 legacy backend dependencies.- Measured against DSH Desktop / Host
0.2.2-rc.1on Windows with real Codex CLI
sessions using the default wait: e.g. 115,901 ms wake onworker_completed,
19,238 ms / 48,975 ms wakes onlead_decision_needed, 37,651 ms on
team_ready_for_review, worker completion → wait wake 44/40 ms, blocker wake
38 ms. Existing 44 native teams and 551 unrelated workspace files were
preserved during the measured deployment. - The DSH Root recorded
rootModelRequests: 0(no root request headers and no
root model responses) in acceptance.
Requirements
- Windows (primary and only tested platform; see limitations).
- Node.js >= 24.
- DSH Desktop / Host
0.2.2-rc.1(the tested version) with the official
experimental Agent Team Profile and Auto Review enabled. - An external MCP-capable client logged in — primarily OpenAI Codex — with
the bridge registered asdeepseek_harness(stdio,node src/server.mjs). - An absolute workspace directory the Team will operate in. Installation of the
adapter is read-only by default; workspace writes require the explicit
-Writeopt-in.
Full installation instructions:
INSTALLATION.md.
Release assets
| Asset | Description | SHA-256 |
|---|---|---|
dsh-mcp-bridge-1.8.0-rc.7.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.7.txt (exact values also in the release description) |
dsh-codex-team-adapter-1.8.0-rc.7.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]. |
Listed in SHA256SUMS-1.8.0-rc.7.txt (exact values also in the release description) |
SHA256SUMS-1.8.0-rc.7.txt |
SHA-256 checksums for the two assets above. | — |
Verify the downloaded files before installing:
Get-FileHash .\dsh-mcp-bridge-1.8.0-rc.7.zip -Algorithm SHA256
Get-FileHash .\dsh-codex-team-adapter-1.8.0-rc.7.tgz -Algorithm SHA256The digests must match the values published in SHA256SUMS-1.8.0-rc.7.txt and in the release description on this page. GitHub's automatically generated "Source code
(zip)" and "Source code (tar.gz)" archives contain the repository at the
v1.8.0-rc.7 tag; the ZIP release asset adds the prebuilt adapter package under
packages/.
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 (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.7.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
~/.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.7 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.1,
Node.js >= 24, Windows. No claim of universal compatibility with other DSH or
Codex versions or with macOS/Linux. - 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. - Auto-archive after 90 days is supported; auto-delete (15 days after
archive) is not implemented, and DSH official Session delete is not
supported. Archive and delete are different features. - Browser screenshot capability is not guaranteed by the bridge; one
release-candidate acceptance case failed to obtain a PNG and is documented as
not verified. - Skills installed only in Codex Skill directories are not automatically
visible to DSH workers. - An existing Codex Desktop stdio MCP connection may cache the previous tool
schema until it reconnects or starts a new session. - Workers sharing one workspace:
writeScopesare collaboration hints, not
file locks; official Auto Review is not an OS sandbox. Use separate git
worktrees if isolation is needed. - No claim of controlled token reduction versus older versions.
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.7(预发布版) 是一个 MCP 桥接服务(注册名
deepseek_harness),让外部 GPT(主要是 OpenAI Codex)成为原生 DeepSeek
Harness Agent Team 中唯一负责推理的 Lead。项目只暴露三个 MCP 工具
(dsh_delegate_task、dsh_team、dsh_team_wait),所有操作都走 DSH 官方实验性
Native Agent Team Service 与 Subagent Runtime:DSH 保留原生 Root Session、Worker、
任务板、消息与生命周期,Root 自身不做任何模型推理(实测
rootModelRequests: 0),规划、决策与最终集成都由外部 GPT 完成。
RC.7 主要变化
- Global Skills 集成:Worker 预设挂载官方 Skill 文件系统与
skill加载器,
Worker 可见的 Skill 目录与原生 Scope 一致;项目.dsh/skills、.agents/skills
优先;Skill 推荐只读目录元数据,模型调用为 0;Skill 正文按需加载。 - 默认 25 分钟等待:省略
timeoutMs时默认等待 1,500,000 ms,任务完成、
真正阻塞、重要授权、严重错误或可集成状态会提前唤醒;普通进度不产生心跳。 - Worker 主动上报阻塞:Worker 通过现有
send_message(首行
[codex:blocking id=... task=task-N])主动报告真实阻塞,桥接层按
Worker/task/revision 持久化并唤醒外部 Lead,Lead 用现有send的
questionId回复;没有新增第四个 MCP 工具。 - 仅按风险做独立审查;外部 Lead 直接完成最终集成;原生 Team 会话持久保存,
Team 在完成且静止 90 天后自动归档。
要求与限制:Windows(唯一实测平台)、Node.js >= 24、DSH Desktop/Host
0.2.2-rc.1(需启用官方实验性 Agent Team Profile 与 Auto Review)、已登录的
Codex 等 MCP 客户端。本版本为 RC 预发布,不承诺与其他 DSH/Codex 版本或
macOS/Linux 的兼容性;Root 零推理不代表总体 Token 成本为零;15 天自动删除未实现,
官方 Session 删除不受支持;浏览器截图能力未经充分验证。完整限制见
Current limitations。
发布物:dsh-mcp-bridge-1.8.0-rc.7.zip(完整源码与构建树,含
packages/ 下的适配器 tgz)、dsh-codex-team-adapter-1.8.0-rc.7.tgz(原生 DSH
插件包)及 SHA256SUMS-1.8.0-rc.7.txt。安装前请校验 SHA-256(见上方资产表)。
本项目为独立第三方开源项目,不是 DeepSeek 官方产品,也未获 DeepSeek
背书;项目自身代码采用 MIT 许可证(Copyright (c) 2026 asdstrind)。反馈与问题请
使用 GitHub Issues。
Release assets and SHA-256
| Asset | Bytes | SHA-256 |
|---|---|---|
dsh-mcp-bridge-1.8.0-rc.7.zip |
551692 | 5ebb04b17e5809d1a01125fa4074e12c4f5a1d3952e77f3c0ad0f4238a891d21 |
dsh-codex-team-adapter-1.8.0-rc.7.tgz |
74474 | 507a7e15209d8515cc6d0b049909104dab52593b064b7d9cee0d0983b13b054b |
SHA256SUMS-1.8.0-rc.7.txt |
200 | c07dad9fa1cf31f2810d56b3db455dcf397e94552ba446d1d800efb48c1812a9 |
Verify the downloaded files:
Get-FileHash .\dsh-mcp-bridge-1.8.0-rc.7.zip -Algorithm SHA256
Get-FileHash .\dsh-codex-team-adapter-1.8.0-rc.7.tgz -Algorithm SHA256Release provenance
- Public source baseline: commit
29fd3f766abadc4d8e37fab5355fa49ae486d5a5(tagv1.8.0-rc.7) of this repository. - The runtime source is the verified
1.8.0-rc.7build: the bundled adapter hostnative-team-plugin/dist/host.mjsrebuilds byte-identically (SHA-256a3f17c2ea964d3bc101f7913366fe45875cecfc2cbecd8395ad3ed13523e3d48) and carries build fingerprinta4139271761854b990d43e9a2bdf269b0cb1b58075507d804da00e27d37d0bdf. - The internally verified
1.8.0-rc.7archive also embedded internal acceptance reports; those were removed for publication, sodsh-mcp-bridge-1.8.0-rc.7.zipwas rebuilt from this public baseline. The prebuilt adapterdsh-codex-team-adapter-1.8.0-rc.7.tgzis byte-identical to the verified artifact. npm teston the public tree: 185 tests passed, 0 failed.node scripts/check-architecture.mjs: 24 source modules, 3 tools, 0 legacy backend dependencies.
中文摘要:本 Release 基于本仓库 v1.8.0-rc.7 标签的公开源码基线构建;运行时源码与已验证的 1.8.0-rc.7 构建一致(适配器 host 可逐字节重建)。公开 ZIP 在移除内部验收报告后由公开基线重新打包,适配器 TGZ 与已验证产物逐字节一致。附件 SHA-256 见上表。本版本是 RC 预发布版,安装要求:Windows、Node.js >= 24、DSH Desktop/Host 0.2.2-rc.1(启用官方实验性 Agent Team Profile 与 Auto Review)。