Agentic coding tools are expensive and slow for one reason: the parent model
reads files one by one. dsh-mcp flips that — the parent agent keeps the
reasoning, the local DeepSeek Harness does the heavy lifting: batch reads,
edits, and command runs, priced at deepseek-v4-flash rates, on your machine.
Works with any MCP client · tested end-to-end with Claude Code
🌐
The pain. Long-horizon, multi-file work is where agentic tools bleed money
and time: the parent model grinds through every file itself — one Read per
file, exploration loops, context that grows and drifts. You pay the parent's
per-token rates for the reading, and you wait for the model to do it
serially.
The fix. One delegate_to_dsh call hands the whole token-heavy subtask to
a fresh, focused DeepSeek Harness agent running deepseek-v4-flash inside
your workspace. All the file I/O happens there — batched, local, cheap. The
parent stays in the loop for what actually needs a brain: planning,
diagnosis, decisions, verification.
Measured on 100 SWE-bench-style long-horizon tasks (heterogeneous model setup: parent = deepseek-v4-pro, DSH = deepseek-v4-flash; arm B runs the same parent model without the plugin):