Blog · Concept
Everything-is-a-plugin vs plugin fatigue
August 14, 2026 · dshbase
The sharpest line in DeepSeek Harness's Hacker News discussion is about its plugin architecture. Supporters call it a genuinely new thing; critics predict plugin fatigue and eventual chaos. Both have a point — the question is what "everything is a plugin" actually means, and whether it's different from what came before.
Why it's not VS Code's plugin system
VS Code has thousands of extensions, but they bolt onto a fixed core: the editor, the debugger, the terminal. You can't replace the core. Claude Code is the same — you customize Skills and MCP, but the product shell is fixed.
DeepSeek Harness inverts this. The core itself — the agent loop, the tools, the UI, the sandbox — is made of plugins. The only fixed piece is Cordis, a kernel that does nothing but load, unload, and resolve plugin dependencies. That's not "plugins on a product"; it's "the product is plugins."
The "Android of agents" narrative
The closest analogy is Android vs iPhone. Android made the OS modular so OEMs and users could swap parts; iPhone kept a sealed whole. DSH's bet is that agents go the Android way — a common kernel with swappable capabilities — rather than the sealed-appliance way. Whether that bet pays off is the open question.
The legitimate concern: plugin fatigue
The critics aren't wrong. Too much modularity has real costs:
- Choice paralysis — if everything is a plugin, what do you install first?
- Compatibility drift — plugins that break when dependencies change.
- Quality variance — an open ecosystem means uneven quality.
DSH's answer so far is presets: the four built-in modes bundle sensible plugin sets so you don't start from zero. You only reach for raw plugins when you need to. That's the pragmatic middle: modular underneath, sensible defaults on top.
The honest take
The plugin architecture is genuinely different from VS Code and Claude Code — but "different" doesn't automatically mean "better." The real test is whether presets + the community keep the chaos at bay while the composability pays off. Watch the ecosystem: it'll decide this argument faster than any blog post.
Related: the architecture deep dive.