Repository navigation
Breaking Changes
-
The supported Host moves from official Desktop
0.2.0-rc.1to0.2.0-rc.2; Host peer versions remain exact, with no compatibility override. -
dsh_delegatenow requires the current Codex task's absolutecwd. The MCP process directory andDSH_DEFAULT_WORKSPACE_CWDno longer substitute for it. -
Delegation reuses or registers the corresponding Desktop Workspace and creates the Session through its
workspaceId. Registration failure does not fall back to an ungrouped Session. -
Upgrade the Desktop plugin and MCP server together. Bridge discovery now requires version
0.2.0; mixed0.1.0and0.2.0installations are rejected.
Added
- Optional
reasoningEffort, validated against the Host model catalog before Workspace or Session creation. - Effort-only requests use the Host current default model; explicit model overrides remain supported.
- Chinese-first and English READMEs, localized architecture diagrams, and a technical reference.
- Version consistency checks for packed artifacts and the MCP handshake.
Compatibility
- Official DeepSeek Harness Desktop
0.2.0-rc.2only. Version0.1.0targeted the older0.2.0-rc.1Host. - Explicit model or effort selection uses the official
selectModelAPI, which may save the Host default selection in the background. - Codex approval guidance is scoped to the manually tested CLI
0.155.1; other versions require their own approval-policy checks.
Verification
- Build, TypeScript checks, and all 33 tests pass, including packed-artifact smoke tests.
- Desktop
0.2.0-rc.2live acceptance through the packed stdio MCP server covers Workspace creation/reuse, GLM 5.3/max, effort-only default selection, event cursors, bounded waiting, and cancellation with retained history. See the technical reference.
Assets
dsh-codex-bridge-dsh-plugin-0.2.0.tgz: install through Desktop Plugins with an absolute tarball path.dsh-codex-bridge-mcp-server-0.2.0.tgz: unpack and runpackage/lib/bin.jswith Node.js.SHA256SUMS: integrity checks for both packages.
Update the plugin and MCP server together. Model provider IDs are deployment-specific; use the exact Desktop model catalog route.