Blog · Comparison

DeepSeek Harness vs Claude Code

August 14, 2026 · dshbase

DeepSeek Harness (DSH) launched in August 2026 as an open-source agent framework positioned squarely against Claude Code. Both let an AI agent read files, run commands, and work through multi-step tasks — but their architecture, licensing, and extension models differ fundamentally. This is the detailed comparison, grounded in a week of running DSH 0.1.0-rc.6 and installing its community plugins.

At a glance

The core difference: plugins vs MCP

DeepSeek Harness treats everything as a plugin — models, tools, sandboxes, session storage, UI, even the agent loop itself are npm plugins installed with dsh plugin add. 100+ first-party plugins ship with the default install. This makes in-process tools trivial to add: one TypeScript module with an apply function.

Claude Code extends through MCP (Model Context Protocol) servers — separate processes exposing tools over a standard protocol. MCP is portable across every MCP-compatible client; plugins are simpler but live inside the dsh process.

The practical trade-off: dsh plugins are easier to write and share (it's just npm), while MCP is more portable (one server works in Claude Code, Cursor, and any MCP client).

Open source & control

DSH is fully open source (MIT) at deepseek-ai/deepseek-harness. You can read the agent loop, fork it, and swap out core parts. Claude Code is closed source — you extend it, you don't own it.

Extensibility in practice

• dsh: dsh plugin add dsh-claude-marketplace — community plugins with verified test results live in the plugin directory.
• Claude Code: add MCP servers, write slash commands and skills, install plugins from marketplaces.

To check whether dsh's plugin model is real rather than aspirational, we tested the ecosystem directly. On dsh 0.1.0-rc.6 we cataloged 101 community plugins in the directory. The breakdown:

• 11 npm packages install and work out of the box.
• 4 need a Web/TUI context to do anything.
• 3 fail to install outright.
• 81 are GitHub-source repos, installed with dsh plugin add github:owner/repo.

That's the honest shape of a week-one ecosystem: two-thirds of it ships as source, not as a registry package. Claude Code's extension story is more polished because MCP and skills are mature and vetted; dsh's is wider-open but expects you to be your own quality gate.

The install experience, honestly

Installing dozens of dsh plugins isn't frictionless. These are the errors you will actually meet, and they don't have Claude Code equivalents because Claude Code never lets you get this close to the internals:

• ERR_PNPM_FETCH_404 — npm mirror lag on a freshly published package. Pin --registry=https://registry.npmjs.org.
• ERR_REQUIRE_ESM — a CommonJS plugin depending on an ESM-only package; the author must rebuild it as ESM.
• Installed but inert — the package lacks a dsh.bundle manifest, so it's dropped in as a plain dependency and never loaded.
• cannot get property "systemPrompt" without inject — a plugin calling ctx.systemPrompt without declaring the inject.
• allowBuilds prompt — git-hosted plugins with a prepare script blocked by pnpm by default.

Every one of these has a one-line fix in our troubleshooting guide. The framing that matters: with Claude Code, the vendor vets what reaches you; with dsh, that vetting is your job — and the append-only session log is what makes it a ten-minute job instead of a lost afternoon.

Pricing

DSH is free — you pay only for the DeepSeek API (or whatever model you point it at). Claude Code is bundled with Claude subscriptions (Pro/Max). The real cost difference is the underlying model pricing, which changes frequently — check current rates before deciding. Note the harness itself moves the bill too: a third-party benchmark found Claude Code cost nearly 7x the cheapest harness per task on the same DeepSeek model (~$0.195 vs ~$0.028), because its request shape isn't built for DeepSeek's prefix caching. See our cost & caching analysis for the numbers.

Which should you choose?

Choose DeepSeek Harness if you want: open source, everything-is-a-plugin, full control, self-hosting, or you're in the DeepSeek ecosystem.

Choose Claude Code if you need: stability, the mature Claude/MCP ecosystem, or tight IDE integration.

FAQ

Can DeepSeek Harness replace Claude Code today?

For developers who want to see and modify the internals, largely yes — with caveats around polish and plugin maturity. For teams that just need a stable tool, Claude Code is still the lower-risk choice.

Is a dsh plugin the same as an MCP server?

No. A dsh plugin is a TypeScript module with an apply function that runs inside the dsh process. An MCP server is a separate process speaking a standard protocol. MCP is more portable; dsh plugins are simpler to write and share.

How mature is the dsh plugin ecosystem?

Early but real: the directory now catalogs 1,100+ community plugins — though in our first test pass, 81 of 101 were GitHub-source and 3 failed to install. It's compounding fast but not yet a vetted marketplace.

Which is cheaper to run?

DSH has no subscription fee and points at DeepSeek's low-cost models; Claude Code is bundled with a subscription. But harness request shape matters — on the same DeepSeek model, Claude Code's harness cost nearly 7x the cheapest option per task.

Bottom line

DSH is the more open, hackable, and rapidly-evolving option — ideal for developers who want to read and modify the internals. Claude Code is the more polished, stable choice. Given DSH's weekly iteration cadence, this comparison will shift fast. Try DSH and judge for yourself — and if you're new to it, start with the tutorial.

All articles →