npx
Quick try
@deepseek-ai/dsh web → :3080
DSH Resources
Browse all curated resources Modes Plugin guide UI skins Contribute FAQ AboutOfficial
DeepSeek Harness turns a model into a working agent on your machine. Use this page to orient, then follow install for the first launch and modes before you load community packages.
One command to start the local Web UI — copy and run in your terminal
npx @deepseek-ai/dsh web npx
Quick try
@deepseek-ai/dsh web → :3080
Cordis
Composition
Load, unload, wire plugins
4 modes
Presets
Standard · PTC · Minimal · Creative
Plugins
Extensibility
Model, tools, sandbox, UI skins
Public materials describe DeepSeek Harness as a locally running coding agent with a Web UI, not a chat toy that only echoes. You point it at a workspace, choose a run mode, and the Agent Loop drives tools through plugins. Capabilities are not hard-wired into a monolith: models, tools, sandboxes, UI skins, and providers register through Cordis. That is why “everything is a plugin” shows up in architecture and the plugin guide.
Developer preview means flags and package surfaces move. Pin what you tested. Prefer the GitHub README when a blog date on this site lags. For a first launch, use a disposable folder — not your entire home directory — as the install page warns.
Product framing also lives on deepseek.com/harness. Source, examples, and releases live in deepseek-ai/deepseek-harness. The runnable package is @deepseek-ai/dsh. This portal rewrites operator paths in English and locales; it does not replace upstream materials when wording conflicts.
Know what DSH is, where GitHub / npm / Web UI fit, and which portal pages own install versus discovery — so you do not invent a second manual.
The harness connects files, terminal, and tools so the model can act in a real workspace instead of stopping at a transcript.
Cordis plugins let you swap providers, tools, and skins without forking core — expand only after Trajectory looks boring.
Commands and APIs follow GitHub and npm. This site links install, modes, tutorials, and curated plugins without inventing star ratings.
1
Need Node.js ^22.19.0 or >=24.0.0. Follow [install](/en/install/) end to end — do not skip the workspace warning.
2
Configure model credentials and a narrow folder. See the [Web UI guide](/en/dsh/web-ui-guide/) for port 3080 and first-task hygiene.
3
Stay in Minimal or careful Standard until Trajectory is dull. Read [modes](/en/modes/) before Creative labs.
4
Browse the [curated directory](/en/plugins/directory/) only after core flows work. Port conflicts belong on [troubleshoot](/en/troubleshoot/).
Official introduction and entry for the DeepSeek Harness developer preview.
Think of DeepSeek Harness as Agent = Model + Harness. The model proposes; Cordis-mounted plugins execute tools and keep session state. Skins and sandboxes load the same way tools do — that is the design bet behind DSH.
When you need chapter form, open tutorials. When you need sibling resource cards, return to the DSH resources hub. Corrections to this portal: contribute.
Start with deepseek.com/harness for product framing and with GitHub for engineering truth. Package identity lives on the npm spoke; full HowTo stays on install so flags do not fork.
Site-level questions (including “is this DeepSeek HQ?”) belong in FAQ. Product bugs belong upstream with Node version, package version, and full CLI output.
After the UI is stable, read the plugin guide. Breadth discovery uses the dsh-plugin topic; community awesome-lists are covered on code-directory. Kernel habits: Cordis. Runtime map: architecture.
Port 3080 already in use, engines mismatch, blank localhost pages, and oversized workspaces are common. Stay on troubleshoot instead of rewriting install here. Pin the npm tag you validated; developer preview moves.
No. Product framing belongs on deepseek.com/harness. This portal is a community guide map: install, modes, tutorials, and plugin notes. Always verify commands against the GitHub README.
Use the steps on install. The usual preview launch is npx @deepseek-ai/dsh web. Then configure model and workspace in the Web UI guide.
After the base UI is stable. Read the plugin guide, then the curated directory. Discovery also happens via the dsh-plugin topic.
See modes. Many people start careful and expand; Creative is for Cordis experiments, not payroll trees.
No. Agent = Model + Harness: the model reasons; DSH connects environment and tools. More aliases and clarifications live on FAQ.
When you are ready to run something local, go to install. For product wording from the publisher, open deepseek.com/harness. Sibling pages stay linked under DSH resources.
Each card opens a full landing page — same hub, different job.
Official MIT open-source repository with source, examples, contribution history, and releases.
Open resource ↗Official @deepseek-ai/dsh npm package for launching the local Web UI.
Open resource ↗Official getting-started notes: configure a model, pick a workspace, run the first task.
Open resource ↗Technical docs on Cordis, plugins, services, session state, and the Agent Loop.
Open resource ↗Spatiotemporal composition framework and plugin service model underneath DSH.
Open resource ↗GitHub projects tagged dsh-plugin — check maintainers and code quality before use.
Open resource ↗Independent community directory of DSH plugins, tools, and infrastructure by category.
Open resource ↗Install DSH, skim architecture and Cordis, or open the Web UI guide before you load community plugins.