"Everything Is a Plugin": Why Cordis Is the Real Bet, Not the Model
DeepSeek's headline pitch for Harness is architectural, not just a model wrapper. Every capability, including models, tools, skills, sessions, sandboxes, storage, the agent loop, scheduling, and the UI, is implemented as a swappable plugin running on top of the Cordis meta-framework [1]. That modularity surfaces in four preset runtime modes: Standard for a full agent toolkit, Code for TypeScript-based multi-step tool orchestration, Minimal (bash plus a file editor) for clean benchmarking runs, and Creator for authoring custom presets with runtime inspection [1]. In practice, developers can select, swap, or extend any capability purely through configuration, without touching the Harness source code itself [1].
That design choice is what technical observers zeroed in on. Hacker News commenters compared Cordis's hot-reload and dynamic enable and dispose plugin model to OSGi, Java's long-standing modular runtime, and to React's component patterns, while noting real limitations around cross-plugin dependencies [2]. The comparison matters because it places Harness's ambitions closer to a platform than a single tool: a repo that already carries an MIT license [3]and lets the community publish plugins under a dedicated GitHub topic [9]is trying to become the substrate other agent tooling builds on, not just another CLI competing with Claude Code.



