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/deepseek-harness DeepSeek Harness source and releases

  • Source of truth
  • Releases & tags
  • Issues with versions

Clone or browse deepseek-ai/deepseek-harness when you need Agent Loop internals, example configs, or a commit hash to cite. Pin the release you tested before filing “broken install” noise.

Open resource ↗ Contribute
  • MIT license on upstream
  • README beats blogs
  • Pin tags you test

Repo

deepseek-ai

deepseek-harness on GitHub

MIT

License

Re-check LICENSE on your pin

Tags

Releases

Match npm before filing bugs

PRs

Contribute

Follow CONTRIBUTING + templates

What the DeepSeek Harness GitHub repo is for

Open github.com/deepseek-ai/deepseek-harness when you need the Agent Loop internals, example configs, or a commit hash to cite in an issue. Developer preview APIs break; issues that omit Node version, exact CLI output, and the commit or package version waste everyone’s time.

Do not paste API keys into Issues or Discussions. Prefer a disposable workspace when reproducing file-edit bugs. Product-facing prose also appears on deepseek.com/harness; the repo remains the engineering source of truth.

Most operators still launch via @deepseek-ai/dsh — see the npm spoke and install. Source builds matter when you patch upstream or follow repo scripts.

Why GitHub stays primary

Flags move in preview

Blog posts and portal pages can lag. The README and release notes on the tag you pin are the authoritative CLI surface.

Reproducible bug reports

Commit hashes, Node engines, and full stderr turn “it broke” into something maintainers can act on.

Contribution clarity

Discussions, Issues, and PR templates live upstream. Portal typos are a different repository — see [contribute](/en/contribute/).

Examples paired with modes

Repo examples often assume a named preset. Pair them with [modes](/en/modes/) so Creative labs never hit payroll trees.

Use the repo without getting lost

  1. 1

    Read README + LICENSE

    Confirm engines and license on the tag you care about before cloning or citing.

  2. 2

    Match Releases to npm

    Compare GitHub tags with what `npx` pulls. Surprises are often mirrors or stale caches — see [npm](/en/dsh/npm-package/).

  3. 3

    Reproduce in a disposable folder

    Narrow workspaces keep secrets out of Issues. Launch path still follows [install](/en/install/).

  4. 4

    File or contribute carefully

    Use upstream templates. Plugin authors usually ship a separate `dsh-plugin` package — [plugin guide](/en/plugins/guide/).

Go deeper

Official MIT open-source repository with source, examples, contribution history, and releases.

Releases, tags, and the npm package

Releases and tags explain what landed; @deepseek-ai/dsh is how most operators launch. Full HowTo steps stay on install so we do not fork two install manuals.

If npx pulls a surprising version, compare the published tag with release notes before filing noise. Mirrors that lag the official registry are a network problem, not a Cordis bug.

How to contribute upstream

Questions belong in Discussions when the project points there; Issues only if the template is open; pull requests must match CONTRIBUTING. Typos on harness-ds.com are a different path — contribute.

Do not treat a docs PR on this portal as an official product decision. Runtime maps: architecture and Cordis.

Security and secrets hygiene

Never paste API keys into Issues, Discussions, or screenshots. Prefer disposable clones when sharing stack traces. Operator safety for community packages is covered in the plugin guide and troubleshoot for local process issues.

FAQ

Should I install from source or npx?

Most operators use npx via install. Source builds matter when you are patching upstream or following repo scripts — details stay on GitHub and the npm spoke.

Where do I report a product bug?

On deepseek-ai/deepseek-harness, with version, Node, and full error text. Portal typos go through contribute.

Is the license MIT?

The public harness repo is published under MIT. Always re-check LICENSE on the tag you pin; third-party plugins have their own licenses in the directory.

How do examples relate to modes?

Repo examples often assume a named preset. Pair them with modes so you do not load Creative experiments into a production tree.

Is this site the same as the GitHub org?

No. harness-ds.com maps guides and SEO pages; engineering truth stays on GitHub. Product HQ framing is on deepseek.com/harness — see FAQ.

Ready to send a fix or ask a precise question? Follow contribute. To run the published package instead of building from source, use install.

More curated DSH resources

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

Back to curated DSH resources →

Around the GitHub spoke

Read the npm package identity, architecture notes, or install steps after you pin a release.