walid@portfolio:~/lab/deepseek-harness$
cd../lab
05ideaSep 2026

One command, one local agent

Running DeepSeek’s open-source agent harness on your own machine

An open-source agent harness you run yourself — the agent loop, the tools and the web interface all execute locally, and every piece is swappable as a plugin. One npx command puts a UI on localhost. The install itself is genuinely a one-liner; the parts worth reading twice are the developer-preview warning, the package-name collision, and the fact that free software does not mean free model calls.

AgentsOpen sourceSelf-hostedPluginsNode.jsThe repo ↗Safety notice ↗Docs ↗Plugin topic ↗Node.js ↗
i
What it is

The machinery around the model rather than the model itself: the agent loop, the tool layer and the interface, all running on your hardware. The architecture is “everything is a plugin”, which is what makes pieces swappable instead of forked. It is MIT licensed and, about a month after first publication, one of the most-starred repositories on GitHub.

!
Three things to know before you install

It is a developer preview — the project says it is iterating fast and that compatibility-breaking changes are expected, so read the safety notice before running it against anything you care about. Install a current Node LTS; an older Node 20 build failed on launch in testing. And take the official package only: other projects use the same short “dsh” name, so match the scoped package in the command below rather than following whatever a tutorial hands you.

The fast path

Launch the web UI

Serves the interface on 127.0.0.1:3080 and opens a browser at it. Add the flag to run the server headless instead.

terminal4 lines
npx @deepseek-ai/dsh web

# server only, no browser window
npx @deepseek-ai/dsh web --no-open
The other path

Build it from source

terminal5 lines
git clone https://github.com/deepseek-ai/deepseek-harness.git
cd deepseek-harness
pnpm install
pnpm run build
pnpm dsh web
Checked, not copied

The numbers, verified on 16 Sep 2026

Every figure below was re-checked against GitHub and the npm registry rather than taken from the write-up.

ClaimStatusWhat it actually is
MIT licensedHoldsThe repository ships an MIT LICENSE, the README states MIT, and every current npm dist-tag agrees. Only the very first release candidate carried a different licence.
Past 225K starsHolds225,959 at the time of writing, on a repository first published in mid-August 2026.
Developer previewHoldsThe published package is still on a release-candidate version, which matches the warning.
300+ pluginsUnderstatedTrue but long overtaken — the curated community index now lists thousands, and the dsh-plugin topic covers 15,026 repositories.
Desktop app is community, not officialHoldsIt is published by a separate organisation, not by DeepSeek. Treat it like any third-party download.

Free software, not free inference

The harness costs nothing and the source is open, but that says nothing about the model calls it makes. Whatever provider you point it at bills you normally, so check how your model is wired up and what that provider charges before setting it on a long task. This is the same trap as every self-hosted agent: the part you install is free, the part that thinks is metered.

If you would rather not use a terminal

✓A community desktop build bundles the harness into an installable app for Windows, macOS and Linux.✓It is not an official product — it comes from a different organisation than the harness itself.✓That makes it exactly as trustworthy as any other third-party installer, which is to say: your call, made deliberately.

The plugin ecosystem is the actual story

Because every capability is a plugin, the ecosystem moved fast. Authors tag their repositories with the dsh-plugin topic, so browsing that topic is the most direct way to see what exists, and a curated community index sits on top of it for the better-known ones.

This is also the part to be careful with. A plugin architecture means third-party code running inside your agent loop with whatever access the harness has — which is the reason the safety notice is worth reading before the plugin list, not after.

i
Provenance

The commands here are as published. The surrounding claims were verified independently against the repository, its LICENSE and README, and the npm registry on 16 September 2026 — the licence, star count and preview status all hold, and the plugin figure was revised upward because the original had been overtaken.

← previous
Website in, React app out
next →
The agent that makes the video
← all experiments