Cordis
Kernel
Register, wire, dispose
Official
DSH Architecture DeepSeek Harness Cordis, plugins, Agent Loop
Use this map to understand why skins and tools load the same way, why modes change tool surface without renaming the loop, and where Creative labs belong before you touch production trees.
- Composition over monolith
- Unload should be boring
- Upstream source wins
Plugins
Capabilities
Model, tools, UI, sandbox
Session
State
Turns, workspace, results
Loop
Runtime
Propose → tool → observe
What DeepSeek Harness architecture means in practice
Cordis supplies spatiotemporal composability: register, wire dependencies, dispose. DeepSeek Harness treats capabilities as plugins on that kernel. Skins, tools, providers, and sandboxes should load and unload without forking core. Deeper kernel context: Cordis spoke and github.com/cordiverse/cordis.
A plugin registers services other plugins consume. Session state carries conversation, workspace bindings, and tool results across turns. Leaking secrets into session logs is an operator error; document filesystem scope in your README as the plugin guide requires.
The Agent Loop proposes actions, invokes tools, and folds observations back into context. Modes change the default tool surface and orchestration style — Standard versus PTC versus Minimal — without renaming the loop itself. Pair this page with modes and architecture chapters in tutorials.
Why operators should care
Debug the stack, not only the model
Haunted sessions are often plugin soup. Unload before blaming inference quality.
Extend without forking
“Everything is a plugin” is operational: swap providers and tools in configuration when Cordis wiring is healthy.
Safer Creative labs
Creative exists so you can inspect runtime wiring without pretending the session is production — [modes](/en/modes/).
Author with disposers
Plugin authors must make unload boring. The [plugin guide](/en/plugins/guide/) is the checklist companion to this map.
Read the map, then operate
-
1
Run a stable UI first
Architecture without a process is sightseeing. Launch via [install](/en/install/) and [Web UI](/en/dsh/web-ui-guide/).
-
2
Learn modes as tool surfaces
Read [modes](/en/modes/). Keep Creative off payroll repositories.
-
3
Study Cordis habits
Open the [Cordis spoke](/en/dsh/cordis/), then upstream Cordis when APIs matter.
-
4
Add one plugin at a time
Use [plugin guide](/en/plugins/guide/) and [directory](/en/plugins/directory/). Source deep-dives: [github](/en/dsh/github-repo/).
Go deeper
Technical docs on Cordis, plugins, services, session state, and the Agent Loop.
Cordis as the composition kernel
If every tool lived inside a single binary, “everything is a plugin” would be marketing. Cordis makes registration and disposal first-class. Product entry: overview. Hub: DSH resources.
Plugins, services, and session state
Curated examples live in the directory. Discovery at scale uses the dsh-plugin topic. Community indexes vs curated cards: code-directory.
The Agent Loop
When the loop “feels drunk”, unload plugins before blaming the model. Soup is not a benchmark. Chapter form: tutorials. Process issues: troubleshoot.
How this maps to day-to-day ops
Install and Web UI get you a process; architecture explains why adding a skin should not require a fork. Contribution paths: contribute. Site FAQ: FAQ. Package identity: npm.
FAQ
Where should I experiment with Cordis wiring?
In Creative per modes, on a disposable workspace. Production trees stay in Standard after unload is boring.
Is architecture documentation the same as the plugin guide?
No. This page is the map; the plugin guide is how you register and dispose packages safely.
Do I need to read Cordis upstream?
Plugin authors should. Operators can skim the Cordis spoke first, then open the Cordis repository when APIs matter.
Where do FAQ-style product questions go?
Does this architecture page speak for DeepSeek product HQ?
No. It is a rewritten operator map on harness-ds.com. Engineering truth stays on GitHub; product framing on deepseek.com/harness.
Architecture without a running UI is sightseeing. Launch via install, then keep modes and the plugin guide open while you add surface area.
More curated DSH resources
Each card opens a full landing page — same hub, different job.
- DSH Official
DeepSeek Harness
Official introduction and entry for the DeepSeek Harness developer preview.
Open resource ↗ - GH Official
deepseek-ai/deepseek-harness
Official MIT open-source repository with source, examples, contribution history, and releases.
Open resource ↗ - npm Official
@deepseek-ai/dsh
Official @deepseek-ai/dsh npm package for launching the local Web UI.
Open resource ↗ - UI Official
DSH Web UI Guide
Official getting-started notes: configure a model, pick a workspace, run the first task.
Open resource ↗ - CO Independent community
Cordis
Spatiotemporal composition framework and plugin service model underneath DSH.
Open resource ↗ - PLG Independent community
dsh-plugin on GitHub
GitHub projects tagged dsh-plugin — check maintainers and code quality before use.
Open resource ↗ - DIR Independent community
DeepSeek Code Directory
Independent community directory of DSH plugins, tools, and infrastructure by category.
Open resource ↗
Build on the architecture map
Study Cordis, follow the plugin guide, or browse curated packages once the Agent Loop feels familiar.