DeepSeek Harness uses Cordis plugin architecture, making models and tools plugins

On October 3, 2026, a report published on Juejin described the architecture behind DeepSeek Harness. According to that account, DeepSeek Harness is built on a Cordis plugin architecture in which models, tools, sessions, sandbox, filesystem, the Agent loop, scheduling, and the UI are all delivered as plugins. The report states that the system contains no fixed kernel that carries business capability. Instead, Cordis handles only a narrow set of responsibilities: maintaining context, service registration, and event dispatch.

In that design, every capability the report names — model access and tool use alongside session handling, sandboxing, filesystem access, the Agent loop, scheduling, and the interface — sits in plugin form rather than in a central core. Plugins are, on this description, the only place where business capability lives, while Cordis itself stays outside that logic and provides context maintenance, service registration, and event dispatch.

The report does not give a release date, version number, or availability details for DeepSeek Harness, and it offers no benchmarks, performance figures, or comparisons with other agent frameworks. No other coverage of the same subject was included in the material, so there is no second account against which the description can be checked. As of this report, the verifiable state of the project is the architectural description alone: model and tool capabilities, together with the other listed components, are implemented as plugins, and Cordis does not carry business logic, limiting itself to context, service registration, and event dispatch. No further developments are recorded in the available material.