dsh-relay

English | 中文

Web-profile helper that diagnoses the Codex MCP launch path and writes host configuration so Codex, Cursor, or Claude Code can spawn dsh --profile codex. It does not run the MCP stdio server in the Web process.

Install into a profile:

dsh plugin --profile web add github:tonytanglab/deepseek-harness-relay-mcp

or install the GitHub Release tarball for a prebuilt lib/. Restart dsh web after install. Then run /relay-setup or ask the agent to call relay_doctor and relay_write_mcp_config.

For a local checkout, build it before adding the directory because pnpm links local directories without running prepare:

pnpm install
pnpm run build
dsh plugin --profile web add file:/absolute/path/to/deepseek-harness-relay-mcp

The plugin accepts both the earlier prerelease Cordis/Schemastery package lines and the current Harness @deepseek-ai/cordis 4.x plus @deepseek-ai/schemastery 3.x line. These peer APIs are supplied by the Harness profile and are optional for package installation. The repository disables pnpm peer auto-installation so building the plugin does not try to fetch Harness-internal transitive packages.

What it does

apply registers one slash command and two tools on the Web profile:

• /relay-setup prints the doctor summary and MCP launch JSON. When mcpConfigPath is set, it also writes that JSON. Extra input is rejected.
• relay_doctor checks that process.argv[1] is an absolute existing dsh entry, that process.execPath exists, and that the credentials path exists, without reading credential contents and without starting MCP stdio.
• relay_write_mcp_config builds the npx launch block from the Codex guide. It writes the block when path is an absolute JSON file, merging mcpServers so other servers remain.

The generated command is npx --yes --package=@deepseek-ai/dsh@0.1.0-rc.7 -- dsh --profile codex. The helper never uses npx.cmd or shell: true, and it never imports StdioServerTransport.

Configuration

Users override rows in the profile cordis.patch.yml. Invalid configuration fails plugin load.

After setup

Point the MCP host at the printed launch block. Session start, wait, steer, and cancel stay on dsh --profile codex, documented in @deepseek-ai/dsh-mcp-codex and the Codex guide. The bundled skill names that workflow.

Model Experience

Tool schema

What the model sees

relay_doctor has an empty parameter object. relay_write_mcp_config requires host as codex, cursor, or claude-code, and accepts optional absolute path.

Token effect

Fixed schema cost on every request where the tools are visible.

KV Cache effect

Prefix-stable while the definitions and visibility are unchanged.

Tool-call history and result

What the model sees

relay_doctor returns JSON with ok, launcher direct/exists/shell: false, workspace roots, and credentials path/exists. It never includes credential file contents. relay_write_mcp_config returns { written, path, host, serverName, config } whose config.args contain --profile and codex. /relay-setup success text starts with DSH Relay is loaded in this Web profile. It does not run the MCP stdio server here. Extra input returns The /relay-setup command does not accept extra input.

Token effect

Per call, bounded by the JSON report and the launch block.

KV Cache effect

Independent of earlier turns.

Known Limitations and Deferred Work

• No in-process MCP stdio — installing this bundle into the web profile does not expose the eleven Codex MCP tools. Those remain on dsh --profile codex.
• No Settings UI — there is no dsh.client form in v0.1.x; /relay-setup and the two tools are the configuration path.