DSH Plugin MarketA community catalog for DeepSeek Harness plugins

dsh-baton

Unconfirmed Models & inference ★ 203 0.6.11

Pass the baton from Claude Code, Codex or any MCP client to a local DeepSeek Harness: an MCP server that hands off tasks, continues a specific session, shows the run live in Harness and hands the result back when it is done.

What it is

Pass the baton from Claude Code, Codex or any MCP client to a local DeepSeek Harness: an MCP server that hands off tasks, continues a specific session, shows the run live in Harness and hands the result back when it is done.

How to install

Run this in the DSH web profile, then refresh the page.

$ dsh plugin --profile web add dsh-baton-mcp@0.6.11

DSH versions accepted

Undeclared

Author and traction

JialaoLiu · ★ 203 · Updated 2026-11-09

About this plugin

Quick start · See it run · How it compares · Token usage · How it works · Tools · Security

Hand coding tasks from Claude Code or Codex to DeepSeek Harness on your machine: the task runs live in the Harness window, the main agent hears back once when it ends, and it gets back the files that changed, the project's own test results and a requirement-by-requirement checklist.Watch it and step in: the task runs live in the Harness window and you can type into it at any time. Every message is labelled "Sent by ChatGPT / Claude from another chat". When Harness stops to ask a question, the main agent answers it if you told it to decide, or brings it to you with its own recommendation.Less of the 5-hour window: a long Codex job takes 16% of a ChatGPT Plus 5-hour window instead of 86% (GPT-6 Astra, the kanban task). The rest of the numbers are under Token usage.Nothing to watch or poll: the main agent waits without polling and gets the result when the run ends. With several runs going at once, each one comes back within a second of finishing.

Needs DeepSeek Harness ≥ 0.2.1-rc.2 (signed in) and Claude Code or Codex. Quick start →What it is

dsh-baton is an MCP server plus a small Harness plugin. The main agent hands the task to an ordinary Harness session with one tool call: you watch it run in the Harness window and can step in at any time, and the main agent hears back once, without polling. Unlike a plain MCP bridge to another model, the work stays visible and the proof comes back with the result.

How it compares Why split the work

Beyond the savings, the split itself helps:A spec before the code. The main agent turns your loose request into clear requirements before handing it over, so Harness gets a clear spec rather than a relayed "build me an X".Checked on evidence. The result carries the changed files, your project's own test output and a point-by-point check against the request; anything missing goes back for another round, instead of taking "done" on trust.The main conversation keeps the decisions. Hundreds of steps of reading files, editing and running tests stay in the Harness session; the main conversation holds your request and the conclusions.

Quick start

Install in one step, check in two.

Nothing else to install: no Node.js, no terminal. It is the same on macOS and Windows.

Install: in Harness, Plugins (插件) → Add plugin (添加插件) → type dsh-baton-host → Install (安装) → Enable now (立即启用). Switched on, the plugin registers dsh-baton for Claude Code and Codex, for every folder, and Harness says so.

Check that it works:

① Open a new chat: in Claude Code or Codex, start a new conversation; one that was already open does not see dsh-baton yet. It is the same in both. Codex asks you to approve MCP tool calls: approve the dsh-baton tools (for unattended codex exec runs, add --approve-for-me).

Similar plugins