DeepSeek Just Changed the Agent Race — by Refusing to Race
发布于 2026-08-16
On August 13, 2026, DeepSeek released its Harness framework as v0.1.0-rc with no compatibility guarantee — and within 24 hours the community had shipped 600+ plugins. This is a strategy-level read on why the 'unfinished' version is the boldest move in the Agent race, what Cordis (the runtime underneath) actually enables, and how the platform-vs-product question just shifted.
DeepSeek Just Changed the Agent Race — by Refusing to Race
If you build frameworks, would you ever push v0.1.0-rc to GitHub and then write "we make no compatibility promise" in the README?
Most teams wouldn't. DeepSeek did.
On August 13, 2026, DeepSeek released DeepSeek Harness (DSH) under MIT — version 0.1.0-rc, no compatibility commitment, with the official repo positioned as "an idea, a reference, and an inspiration" rather than a canonical answer (https://github.com/deepseek-ai/deepseek-harness).
Within 24 hours, the GitHub topic dsh-plugin had attracted 600+ community plugin repositories. Long-term memory. Virtual pets. A Web retro-games collection. Terminal UIs.
That is not a normal open-source launch.
This might be the calmest high-stakes bet in the Agent space this year.
What DSH actually is
One sentence: DSH splits the Agent into two halves.
Agent = Model + Harness
The model is the brain. The Harness is the nervous system plus work environment — context, tools, filesystem, memory, permissions, sandbox, Agent Loop, and the interfaces that touch the real world.
But the interesting part isn't the formula. It's the foundation.
DSH is built on Cordis — Shigma's open-source Meta-Framework, vendored into the repo as @deepseek-ai/cordis. Cordis isn't new. It's been battle-tested in production by Koishi, a cross-platform chatbot framework that serves QQ, Discord, Telegram, and WeChat. Koishi's job every day is "dozens of plugins hot-swapping, configurable on the fly." That's the same shape as an Agent runtime — minus the LLM.
