Dsh Baton

What dsh-baton does

dsh-baton hands coding work from Claude Code or Codex to a DeepSeek Harness running on the same machine. The task executes in a regular Harness session, where a developer can watch the work and intervene through the Harness interface. After the run finishes, the calling agent can receive the result rather than repeatedly checking the session.

The bridge is useful for large or long-running implementation tasks. A handoff can continue an existing Harness session or create one in a selected workspace or working directory. The returned result can contain the files created, modified, or deleted, the project's test output, and a checklist matching the request's requirements.

How it works

Install and enable the dsh-baton-host plugin from the Plugins area in DeepSeek Harness. Once enabled, it registers the MCP tools for Claude Code and Codex. The Harness installation must be signed in and meet the required minimum version, and the supported desktop platforms are macOS and Windows.

A typical flow is:

1. Discover a workspace, session, or available model.
2. Send a self-contained request with dsh_send.
3. Wait for completion with dsh_wait, optionally using the returned background wait command.
4. Read status, answer Harness questions, or cancel the run when needed.
5. Continue the same session with a follow-up request.

For bigger jobs, split independent parts across separate sessions and assign each part clear file ownership. When a run pauses for a person, dsh_wait reports the question or approval state; dsh_answer relays answers for questions that can be answered through the agent.

Setup and configuration

The normal setup requires no Node.js, terminal installation, or dependency installation. In Harness, open Plugins, add dsh-baton-host, install it, and enable it. Codex users must also trust the dsh-baton: waiting for the Harness run hook in Codex settings so Codex can be woken when a run ends instead of checking repeatedly.

If Harness cannot register the server, npx -y dsh-baton-mcp setup performs the registration and requires Node.js 22.15 or newer. Codex may request approval for MCP calls; unattended codex exec runs can add --approve-for-me.

Tools and capabilities

• dsh_list_workspaces finds Harness project folders and returns workspace IDs for later sends.
• dsh_list_sessions searches recent sessions by limit, working directory, or query.
• dsh_list_models shows available providers, model IDs, names, reasoning efforts, and the default model.
• dsh_read_session reads recent messages and called-tool names, without tool output.
• dsh_send starts a run or continues a session, with queue and steer modes for busy sessions.
• dsh_status checks a run without waiting; dsh_wait waits for its final state.
• dsh_answer responds to questions from a waiting Harness run.
• dsh_cancel stops activity and can remove queued messages; dsh_call invokes an additionally registered dsh-baton tool by name.

Limitations and notes

The workspace and model discovery tools require the dsh-baton-host plugin. Session listing has no pagination, so use a larger limit or narrow the search. A session absent from the listing should be treated as archived or gone rather than located by inspecting files.

dsh_wait waits for up to 50 seconds per call; repeat it with the same run ID after a timeout. dsh_status is for inspection only and does not replace waiting. Reading a session returns message text and tool names, but not tool output. Messages sent to Harness must be self-contained because Harness does not receive the surrounding conversation.