Two and a half months. 255 thousand stars.
The DeepSeek Harness, the dsh, was created on August 13 with one sentence as its manifesto: everything is a plugin. On Tuesday, the repository passed 255 thousand stars on GitHub, with 31 thousand forks and MIT license.
The speed, on a timeline
Over 33 thousand stars in hours on launch day, 150 thousand marked by the press a week later, and over a quarter of a million now. It is the fastest adoption the agent ecosystem has recorded, and it happened in a version 0.2 project.
The architecture that explains the why
In the dsh, the model adapter, the tool registry, the session log and the agent loop itself are replaceable plugins. The Chinese launch coverage summarized it: there is no privileged core to patch.
The ecosystem followed the design: a desktop client with 32 thousand stars, a plugin catalog with almost 20 thousand, and sandboxing per operating system, from Landlock on Linux to Windows ACL.
The honest warning
The project is at version 0.2, with breaking changes announced in the README, and it does not accept external PRs. The requested contribution is a plugin, not a patch.
That design has a practical consequence for adopters: you do not fix the harness, you replace it or extend it via plugin. The operation needs to be ready for that maintenance model, with version isolation and a written update policy.
The battle changed fields
The applied AI battle left the model and moved to the harness. When the agent loop becomes a plugin, the differentiator stops being whoever has the bigger model and becomes whoever orchestrates better.
It is the third confirmation of the same pattern this year. SantanderAI open-sourced guardrails, bridges and frameworks because infrastructure is not the differentiator. MiMo Code showed that the same model scores differently depending on the harness. And now the dsh makes the loop itself replaceable by design.
At Tech86, agent operation standardization is a project: harness choice, plugin policy, sandbox and flow documentation.
Conclusion
255 thousand stars in 75 days say the market wants this architecture. The question left for operators is not whether to adopt a modular harness, it is whether to adopt it with the discipline it demands: plugins as supply chain, sandbox by default, and the flow documented before the contract. When the loop becomes a plugin, orchestration is the product.