On August 13, DeepSeek released its official agent harness, DeepSeek Harness (DSH). Three days later it has passed 113,000 GitHub stars — the single biggest event in the agent-tooling world this week, and arguably the fastest star growth of any agent project this year. Its tagline is simple: "Everything is a Plugin."
For developers, DSH matters beyond the star count. The plugin marketplace forming around it looks a lot like the early MCP ecosystem — and the same playbook that worked for MCP tools is being replayed here, faster.
DSH is a local-first agent harness built on the Cordis plugin architecture. You install it with a single command and get a full agent environment immediately:
npx @deepseek-ai/dsh webThat boots a web UI on 127.0.0.1:3080 — no cloud account, no API gateway, no vendor lock-in. Desktop, web-UI and TUI variants all exist, and the architecture treats every capability (tools, UI panels, routing, memory) as a pluggable module rather than a hardcoded feature.
In just three days, a full satellite ecosystem has appeared. Each of these was created between August 13 and 16:
| Component | Stars | Role |
|---|---|---|
| deepseek-harness (core) | 113,000+ | Official agent harness, MIT licensed |
| deepseek-harness-desktop | 5,600+ | Desktop GUI client |
| dsh-web-ui | 2,700+ | Browser-based UI |
| awesome-dsh-plugin | 2,900+ | Curated plugin marketplace list |
| dsh-TUI | 1,200+ | Terminal interface |
| routing-suite | 1,600+ | Multi-model routing plugins |
Six 1,000+ star projects spawned from one release in under a week. That is the "plugin gold rush" pattern we saw in the MCP ecosystem in 2025 — but compressed into days instead of months.
The harness market went through three phases. First came monolithic agents (everything bundled). Then came MCP, which standardized the tool interface but left the harness itself closed. DSH represents the third phase: the harness itself is modular, and every extension point — tools, panels, routing, memory, skins — is a plugin you can install, publish, or sell.
For MCP developers this is a familiar shape. DSH plugins are not a replacement for MCP; they are a complementary layer that sits on top of agent infrastructure. The immediate opportunity is to package existing MCP servers as DSH plugins and get listed in awesome-dsh-plugin while the marketplace is still young.
DSH is in developer preview. Breaking changes are frequent, and production dependence is not yet wise. Treat it like the MCP ecosystem in mid-2025: build, experiment, publish early — but keep interfaces thin so you can adapt as the API settles.
If you want to explore the ecosystem without committing to it:
npx @deepseek-ai/dsh web and try the default plugin set.awesome-dsh-plugin list to see which categories are already crowded and which are empty.For web data specifically, our Unified Scraper MCP and B2B Lead Finder MCP cover the scraping side of an agent stack — and the same principles from our MCP scraping guide apply when wiring them into any harness, DSH included.
DSH's 113K-star week is the strongest signal yet that plugin-first agent infrastructure is the direction of travel. For developers, the practical move is the same as it was with MCP: pick the empty niches, ship small plugins early, and build on interfaces that keep your options open. The ecosystem is three days old — the floor is still open.