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

DSH Web UI Guide local :3080 — not a cloud online app

  • Localhost Web UI
  • Model + workspace
  • First safe task

Assumes you already followed install once. Leave the terminal running, open the printed URL, configure credentials carefully, and keep the workspace root narrow until Trajectory looks boring.

Open resource ↗ Open install guide
  • Commonly :3080
  • Keys stay local
  • Narrow workspace first

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

npx @deepseek-ai/dsh web

3080

Typical port

Conflicts → troubleshoot

Model

Credentials

Official platform keys

Folder

Workspace

Disposable clone preferred

Modes

Presets

Minimal / careful Standard

What the DeepSeek Harness Web UI is for

After launch, the Web UI is the operator console: model credentials, workspace root, mode selection, and the task box that drives the Agent Loop. It is not a cloud IDE hosted by this portal — the process runs on your machine, usually reachable at http://127.0.0.1:3080.

Run the launch command from install inside or near the project you intend to touch. The process prints a local URL; leave that terminal running. If nothing listens on the expected port, check troubleshoot before killing random Node processes.

Browser extensions that rewrite localhost can produce empty shells that look like product bugs. Try a clean profile when the HTML loads but controls never hydrate. Package identity questions belong on npm; source questions on github.

Why this guide exists

First hour failure modes

Wrong port, blank pages, oversized workspaces, and reckless modes create “haunted” sessions that look like model bugs.

Credentials hygiene

Keys belong in the local UI — never in GitHub Issues, Discord screenshots, or shared Trajectory dumps.

Mode discipline

Minimal and careful Standard keep blast radius small; Creative is a lab. Details: [modes](/en/modes/).

Path to depth

This page is a checklist; chapter form lives under [tutorials](/en/tutorials/) once the first task is boringly correct.

From launch to first task

  1. 1

    Launch and keep the process up

    Use [install](/en/install/) steps. Leave the terminal open; note the printed localhost URL (often :3080).

  2. 2

    Add model credentials

    Enter API credentials from the official DeepSeek platform. Never paste keys into public issues.

  3. 3

    Choose a narrow workspace

    Pick a disposable clone — not home directories mixed with secrets. Watch Trajectory after a one-line task.

  4. 4

    Pick mode, then deepen

    Start careful per [modes](/en/modes/). Next: [tutorials](/en/tutorials/). UI misbehavior: [troubleshoot](/en/troubleshoot/).

Go deeper

Official getting-started notes: configure a model, pick a workspace, run the first task.

Launch and reach the UI

Confirm Node engines match upstream before blaming the UI. If 3080 is occupied, free the port or follow alternate bind notes on troubleshoot. Product entry context: overview.

Architecture context for what the UI is driving sits in architecture. Cordis composition habits: cordis.

Model credentials and modes

Wrong mode plus a huge plugin stack produces noisy sessions. Unload what you do not need; the plugin guide assumes adds are reversible. Curated packages: directory.

PTC versus Standard decisions belong on modes — do not invent a fifth preset in a sticky note.

Workspace root and first task

Start with list files, run tests, or apply a one-line comment. Expand only when Trajectory looks boring. Chapter-length walkthroughs: tutorials. Hub: DSH resources.

When the UI misbehaves

Port in use, npx cache weirdness, Node engines errors, and permission denied on the workspace are documented on troubleshoot. Site-level questions: FAQ. Portal corrections: contribute.

FAQ

I never see the UI on port 3080

Follow troubleshoot for bind failures and conflicts. Confirm the install steps on install still match the README.

Where do I learn the UI beyond this checklist?

Use tutorials for chapter form. Modes and plugin loading are separate skills — modes and plugin guide.

Can I point the workspace at my entire disk?

You can, and you should not on day one. Narrow roots keep blast radius small; see workspace warnings on install.

Is there an online DeepSeek Harness I can open without installing?

No hosted cloud UI. Start npx @deepseek-ai/dsh web on your machine and open http://127.0.0.1:3080/. Keys stay local. Launch steps: install.

Is this Web UI guide the DeepSeek product site?

No. This is a community operator checklist on harness-ds.com. Product materials: deepseek.com/harness. More: FAQ.

When the first task looks boringly correct, deepen with tutorials. If the server never binds, stay on troubleshoot until localhost responds.

More curated DSH resources

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

Back to curated DSH resources →

Next after the Web UI

Troubleshoot port issues, pick a safer mode, or return to install if the package never launched.