Skip to content
DeepSeek Harness DSH
English
English 简体中文 繁體中文 日本語 한국어 Español
Quick start
Menu
Home Tutorials Plugins Install Troubleshoot Compare Blog

DSH Resources

DeepSeek Harness Official introduction and entry for the DeepSeek Harness developer preview. deepseek-ai/deepseek-harness Official MIT open-source repository with source, examples, contribution history, and releases. @deepseek-ai/dsh Official @deepseek-ai/dsh npm package for launching the local Web UI. DSH Web UI Guide Official getting-started notes: configure a model, pick a workspace, run the first task. DSH Architecture Technical docs on Cordis, plugins, services, session state, and the Agent Loop. Cordis Spatiotemporal composition framework and plugin service model underneath DSH. dsh-plugin on GitHub GitHub projects tagged dsh-plugin — check maintainers and code quality before use. DeepSeek Code Directory Independent community directory of DSH plugins, tools, and infrastructure by category. Browse all curated resources Modes Plugin guide UI skins Contribute FAQ About
English
English 简体中文 繁體中文 日本語 한국어 Español

Official

@deepseek-ai/dsh DeepSeek Harness npm package and npx Web UI

  • Scoped @deepseek-ai/dsh
  • npx Web UI launch
  • Pin versions you test

Treat npm as the delivery channel and install as the driver’s manual. After the package is on disk, configure model and workspace in the Web UI guide.

Open resource ↗ Open install guide
  • Scoped DeepSeek AI package
  • Node engines enforced
  • HowTo on /install/

One command to start the local Web UI — copy and run in your terminal

npx @deepseek-ai/dsh web

npm

Package

@deepseek-ai/dsh

npx

Try command

npx @deepseek-ai/dsh web

3080

Common port

Conflicts → troubleshoot

Node

Engines

^22.19.0 or >=24

What @deepseek-ai/dsh is

The scoped package is @deepseek-ai/dsh. Engines commonly require Node.js ^22.19.0 or >=24.0.0; older 18/20 lines fail early. The package is the distribution channel; GitHub remains the source and release narrative.

Search aliases (DS Harness, deepseek-harness) still resolve to this package name when you launch. Do not confuse community forks or random dsh typosquats with the scoped DeepSeek AI package.

The widely documented try command is npx @deepseek-ai/dsh web. It fetches the preview package (unless cached) and starts the local Web UI — often on port 3080. Keep the terminal open while you work. Exact flags, env vars, and source-build alternatives belong on install.

Why a dedicated npm spoke

Identity without duplicating HowTo

SERP queries for the package name need a clear identity page; install owns OS checklists so we never maintain two manuals.

Engines and typosquat awareness

Wrong Node versions and similarly named packages waste hours. Scope and engines are first-class facts here.

Version pins in preview

Yesterday’s blog may cite a moved tag. Pin what you validated in CI or a team README.

Bridge to UI and modes

Package metadata does not replace Cordis hygiene. After launch, follow [Web UI](/en/dsh/web-ui-guide/) and [modes](/en/modes/).

From package identity to a running UI

  1. 1

    Follow install, not this page

    Prerequisites, verify, and source builds: [install](/en/install/). This spoke stays about package identity.

  2. 2

    Run the documented one-liner

    `npx @deepseek-ai/dsh web` — leave the process running. Bind failures: [troubleshoot](/en/troubleshoot/).

  3. 3

    Configure model & workspace

    Use the [Web UI guide](/en/dsh/web-ui-guide/). Prefer a disposable folder on day one.

  4. 4

    Add plugins later

    Core does not auto-load community packages. See [plugin guide](/en/plugins/guide/) and [directory](/en/plugins/directory/).

Go deeper

Official @deepseek-ai/dsh npm package for launching the local Web UI.

What npx @deepseek-ai/dsh web does

The command resolves the scoped package, may download a preview build, and starts the local Web UI. Corporate mirrors that lag the official registry produce confusing “old package” symptoms — prefer the registry upstream documents.

Product framing: overview. Source narrative: github. Operator hub: DSH resources.

Version pins and mirrors

Developer preview means published tags move. Record the exact version in CI. If engines mismatch, upgrade Node — do not force engines on a payroll machine. Chapter walkthroughs: tutorials.

Plugins are not included by default

Installing the package gives you the harness surface. Community tools arrive later via Cordis. Safety checklist: plugin guide. Breadth: dsh-plugin topic.

FAQ

Where are the full install steps?

Only on install — prerequisites, OS notes, verify, and source builds. This npm page stays about package identity.

What is the one-liner to try the Web UI?

npx @deepseek-ai/dsh web — then follow Web UI for model and workspace. Port issues: troubleshoot.

Does installing the package load community plugins?

No. Core comes from the package; community packages are added later via the plugin guide and directory.

npm says engines mismatch — what next?

Upgrade Node to the range upstream documents, then retry from install. Do not force engines on a payroll machine.

Is harness-ds.com the publisher of @deepseek-ai/dsh?

No. The package is published by DeepSeek AI on npm. This site explains identity and links to install; it is not product HQ — see FAQ.

Treat npm as the delivery truck and install as the driver’s manual. When the package is on disk, open the Web UI guide and keep modes conservative until Trajectory is boring.

More curated DSH resources

Each card opens a full landing page — same hub, different job.

Back to curated DSH resources →

After you understand the package

Install with the full HowTo, read Web UI setup, or return to the DSH overview for product framing.