The deepseek-ai/deepseek-harness repository went public on June 10, 2026 with a premise that took a while to sink in: everything is a plugin. The runtime, the CLI, the web UI, even the agent skills — all of it loads through the same plugin interface. If you have been trying to understand the deepseek harness plugin architecture, this is the mental model to start with.
The dsh Runtime at the Center
The dsh runtime is the process that loads and executes plugins. It defines the lifecycle — discover, load, validate, run — and it is what enforces the dsh.bundle contract. Plugins declare their entry points in the bundle; the runtime resolves dependencies and sandboxes execution where the platform allows.
Cordis Core as the Kernel
Underneath the runtime sits Cordis core, the dependency-injection kernel inherited from the Cordis framework. It wires services, manages contexts, and gives plugins a predictable environment to talk to each other. Understanding Cordis matters because plugin configuration, context isolation, and service overrides all flow through it.
The Python SDK for Plugin Authors
Most plugins are written against the official Python SDK, which wraps the runtime contract in familiar Python: a class, a few decorators, a bundle manifest. The SDK hides most of the machinery — but knowing it is there helps when a plugin misbehaves, because the error almost always traces back to a contract violation the SDK tried to smooth over.
Why the Architecture Matters for Installers
- Everything being a plugin means every piece of code you install gets the same runtime privileges — and the same risk profile.
- The dsh.bundle declaration is the one contract the runtime checks; its absence is a legitimate warning.
- Cordis-based isolation is only as strong as the sandbox beneath it (see our Landlock deep dive).
Once you see the architecture as one plugin interface with a kernel underneath, the ecosystem stops looking chaotic. It also becomes clear why quality scoring and security scanning of individual plugins matter so much.