Open Source

DeepSeek Harness: The Open-Source Agent Framework Where Everything Is a Plugin

DeepSeek open-sourced its agent harness (dsh) under MIT — 25.9k stars, powered by the Cordis plugin framework, with nine specialized sub-agents, MCP support, sandboxing, and a Web UI. 'Model + Harness = Agent' is the new industry formula, and DeepSeek just shipped the reference implementation. Architecture, benchmarks vs Claude Code, strategic significance, and honest caveats.

Keeping this site alive takes effort — your support means everything.
無程式碼也能輕鬆打造專業LINE官方帳號!一鍵導入模板,讓AI助你行銷加分! 無程式碼也能輕鬆打造專業LINE官方帳號!一鍵導入模板,讓AI助你行銷加分!
DeepSeek Harness: The Open-Source Agent Framework Where Everything Is a Plugin

Key takeaways

  • DeepSeek Harness (dsh) is DeepSeek AI's open-source agent framework — 25.9k stars, MIT license, 12,000+ commits — built on the Cordis meta-framework where literally everything (models, tools, sessions, sandboxes, loops, UI) is a plugin that can be mixed, matched, replaced, and extended.
  • The industry formula 'Model + Harness = Agent' is now concrete: the model reasons, the harness handles everything else — tool execution, memory, context control, sandboxing. dsh ships 9 specialized sub-agents (file picker, editor, reviewer, browser-use, planner, researcher, terminal runner, deep thinker, follow-up suggester) instead of one giant model in a loop.
  • Run it in one command: npx @deepseek-ai/dsh web starts the Web UI at http://127.0.0.1:3080. DeepSeek V4 Pro for hard reasoning, Kimi K2.6 for big context, Miniax M2.7 for UI work, V4 Flash for cheap edits — with mid-session model swapping that Claude Code doesn't offer.
  • Strategic significance: owning the harness layer maximizes DeepSeek's 50x prompt-caching price delta (cached vs fresh input tokens), and it's part of a Chinese-lab harness wave — Alibaba Qoder, Moonshot Kimi Code, Zhipu Zcode — as foundation models commoditize and loyalty moves to the workflow layer.
  • Honest caveats: v0.1 developer preview with explicit compatibility-breaking changes, a young plugin ecosystem, multi-agent overhead (more moving parts, more failure points), and DeepSeek's models have a documented jailbreak history (Cisco found 100% attack success on HarmBench for R1) — use strict tool boundaries and guardrails.

Key answers

What is DeepSeek Harness?

DeepSeek Harness (dsh) is DeepSeek AI's open-source agent harness — the engineering layer that wraps LLMs and turns them into reliable coding agents. It's the concrete realization of 'Model + Harness = Agent': the model provides reasoning, the harness handles tool execution, memory, context control, sandboxing, and orchestration. Powered by the Cordis plugin framework, every component is a plugin. It's MIT-licensed, 25.9k stars, and runs via npx @deepseek-ai/dsh web.

What does 'everything is a plugin' mean in dsh?

In DeepSeek Harness, models, tools, skills, session state, databases, sandboxes, filesystems, execution loops, orchestration layers, and the UI are ALL implemented as plugins on the Cordis framework. There is no privileged core to patch — you extend dsh by mounting a plugin beside the others, and registrations unwind when the plugin unloads. This means security boundaries can be hardcoded (a read-only agent simply has no write tools registered) instead of relying on prompt-level instructions that degrade in long sessions.

What are the 9 sub-agents in DeepSeek Harness?

Instead of one giant model in a loop, dsh orchestrates specialized sub-agents: a file picker (selects only relevant files to avoid context dilution), planner (breaks tasks into steps with an /in interview command), editor (precise surgical diffs instead of whole-file rewrites), code reviewer (flags risky edits before they ship), browser-use (drives a real Chromium instance for QA), researcher (pulls docs and external context), terminal runner (executes shell commands), deep thinker (optional, calls premium models for hardest reasoning), and a follow-up suggester. Each uses a model tuned for its job.

How does dsh compare to Claude Code and other harnesses?

Independent testing of DeepSeek V4 Flash across 8 harnesses on 30 multi-SaaS workflows showed Claude Code at 53.3% pass rate ($0.195 per success, only 1.5% cache hits), OpenCode 46.7% ($0.073), Codex 53.3% ($0.081, ~70% cache hits), and Hermes Agent 50% ($0.056). dsh's advantages are multi-model swapping (Claude Code locks you to Anthropic), sub-agent specialization that reduces context dilution on multi-file work, and native optimization for DeepSeek's cheap context-caching API.

Is DeepSeek Harness production-ready?

Not yet. It's in v0.1 developer preview with an explicit warning: 'THERE WILL BE COMPATIBILITY-BREAKING CHANGES.' The plugin ecosystem is young compared to mature platforms. A public beta was planned for August 13, 2026, coinciding with DeepSeek-V4-Pro GA. The core architecture is solid and MIT-licensed, but treat it as a preview — expect to update plugins and scripts as it iterates.

DeepSeek Harness: The Open-Source Agent Framework Where Everything Is a Plugin

The formula is everywhere now: Model + Harness = Agent.

The model reasons. The harness handles everything else — tool execution, memory, context control, sandboxing, orchestration. And on August 2026, DeepSeek shipped what might be the most important open-source reference implementation of that formula yet.

DeepSeek Harness (dsh) is the Chinese lab’s open-source agent framework: 25.9k stars, MIT license, 12,000+ commits, and an architecture built on one radical idea — everything is a plugin.

“Models, tools, skills, sessions, sandboxes, filesystems, loops, orchestration, and UI are ALL implemented as plugins, and can be mixed, matched, replaced, and extended.”

The architecture: Cordis under everything

dsh is powered by Cordis, a plugin meta-framework whose design is described in a paper on spatiotemporal composability. What that means in practice:

  • No privileged core. Every part of the product — model adapter, tool registry, session log, even the agent loop itself — is a plugin. You extend dsh by mounting a plugin beside the others, and registrations unwind when the plugin unloads.
  • Layered composition. A running dsh is a plugin tree composed from profiles and bundles (dsh-base provides model adapters, tools, sandbox, approval policy; dsh-web-app adds the browser UI; dsh-headless is a one-shot runner). Every row in the config tree can be replaced by a patch of your own.
  • Hardcoded security. Because restrictions live in the tool registry, not the prompt, a read-only agent simply has no write tools registered. One HN commenter summed it up: “Prompt-level restrictions hold right up until a long session starts improvising, and then you find out.”

Run it in one command

npx @deepseek-ai/dsh web

That starts the Web UI at http://127.0.0.1:3080 — a local browser portal for visualizing agent sessions, tool outputs, and configuration. (Or clone and build with pnpm.)

The 9 sub-agents: why multi-agent beats one big loop

Most coding agents are one large model in a loop — read files, plan, edit, test, review, all from the same brain. That works for tiny tasks and falls apart on anything touching more than a couple of files.

dsh takes the opposite approach: nine specialized sub-agents, each with a narrow job and a tuned model:

Sub-agentJob
File pickerScans the codebase, pulls only relevant files (uses cheap Gemini 3.1 Flash Lite for retrieval — less context noise = sharper output)
PlannerBreaks big tasks into ordered steps; /in interview command asks questions first
EditorPrecise surgical diffs instead of whole-file rewrites — no formatting drift
Code reviewerReviews every change, flags risky edits before they ship
Browser-useDrives a real Chromium instance — clicks, fills forms, screenshots, reads back what it sees
ResearcherPulls docs and external context
Terminal runnerExecutes shell commands, reads back output
Deep thinkerOptional; calls premium models (e.g. GPT-5.4) for the hardest reasoning
Follow-up suggesterDrops three clickable next actions after every response

Main coding brains are swappable mid-session: DeepSeek V4 Pro for complex multi-file work, Kimi K2.6 for massive context analysis, Miniax M2.7 for UI/creative, DeepSeek V4 Flash for fast cheap edits. That’s a flexibility Claude Code doesn’t offer on its default plans.

The honest benchmark picture

Independent testing of DeepSeek V4 Flash across 8 harnesses on 30 multi-SaaS workflows (Airtable, Gmail, Sheets, GitHub, Slack, PostHog — 240 runs, 53.8% overall pass rate):

HarnessPass rateMedian timeCost per success
Pi Agent66.7%132.2s$0.028
Prime Agent62.5%242.1s$0.131
OMP56.7%272.4s$0.103
Claude Code53.3%122.7s (fastest)$0.195 (only 1.5% cache hits)
Codex53.3%245.0s$0.081 (~70% cache hits)
DeepAgents53.3%187.1s$0.045
Hermes Agent50.0%175.5s$0.056+
OpenCode46.7%129.7s$0.073

The cost column is the story: Claude Code used almost all fresh-input tokens (1.5% cache hit) vs Codex’s ~70% — and fresh input costs ~5x cached. dsh’s native optimization for DeepSeek’s context caching is exactly where that delta lives.

Why DeepSeek built this: strategy

  1. Own the agent layer. Model providers historically left tooling to third parties. But developer loyalty now lives at the workflow layer — and every frontier lab wants to control the runtime that burns their tokens.
  2. Maximize the 50x caching delta. DeepSeek’s API prices cached input at roughly $0.02/M vs $1/M fresh — a 50x difference. A harness that front-loads stable prompt sections (system rules, tool definitions) captures cache hits that generic third-party clients routinely destroy.
  3. Custom API tailoring. DeepSeek’s automatic-prefix-cache differs from Kimi’s moonshot-context-cache; each provider has its own error codes, retry semantics, streaming formats. A native harness implements the exact behaviors its own API needs — including MCP schema cleaning (flattening $ref and anyOf so models generate valid params).

It’s also part of a wave: Alibaba Qoder, Moonshot Kimi Code, Zhipu Zcode — Chinese labs shipping native harnesses as foundation models commoditize and the fight moves to the workflow layer.

The honest caveats

  • Developer preview. v0.1 with an explicit warning: “THERE WILL BE COMPATIBILITY-BREAKING CHANGES.” A public beta was slated for August 13, 2026, coinciding with DeepSeek-V4-Pro GA. Expect to update plugins regularly.
  • Young plugin ecosystem. Cordis is powerful but the community plugin catalog is small next to VS Code or mature agent frameworks.
  • Multi-agent overhead. Nine sub-agents = more moving parts, more latency, more points of subtle failure than a single-model loop.
  • Model safety history. Cisco’s assessment of DeepSeek R1 found a 100% attack success rate on HarmBench jailbreaks — cost-efficient training appears to have compromised guardrails. Use strict tool boundaries (which dsh’s plugin architecture enables) and third-party guardrails for anything sensitive.

Conclusion

DeepSeek Harness is the clearest open-source expression yet of the Model + Harness = Agent paradigm. The “everything is a plugin” architecture is genuinely different — not a wrapper around a loop, but a composable runtime where the model adapter, the tools, the sandbox, and the UI itself are swappable parts.

It’s a preview, not a production platform — the breaking-changes warning is real, and the ecosystem needs time. But for developers who want to understand where agent engineering is heading, or who want a MIT-licensed harness natively optimized for the cheapest frontier API on the market, dsh is the reference to study. Everything is a plugin — and that’s the future of agent architecture.