Choose a test folder
Use a folder without secrets or production code for your first run.
Start with the official Web UI, then pick community plugins when you know what you need.
Official command
npx @deepseek-ai/dsh web⚠ Copy this command exactly. Packages with similar names are not DeepSeek Harness.
DeepSeek Harness is still in developer preview. Start small, expect changes, and add plugins only when you understand what they do.
Use a folder without secrets or production code for your first run.
It opens the Web UI on your machine. Leave the terminal running while you use it.
Get comfortable with the local workspace before you connect more tools or services.
Plugins are third-party code. Read the source, permissions, and version notes before you install one.
Answer three quick questions to see whether it matches how you work today.
You want a local workspace and are comfortable with preview software. Run the official command first; plugins can wait.
A local browser interface. It is the easiest place to begin.
A keyboard-first option if you prefer to work from a shell.
Use them with a local folder only after you know what they can read or change.
Harness runs locally, but your model provider and connected services may charge separately.
A local interface does not mean every request stays on your machine. Check your provider, tools, and plugins.
Use plugins in a test workspace first. Check permissions and never paste credentials into prompts you do not trust.
Browse community plugins by use case. Each listing includes the publisher link, a review label, and the risks to check before installing.
No. This is an independent guide. The command and repository links take you directly to DeepSeek.
Not necessarily. Check the listing label, the risk tags, and the publisher documentation before you install it.
Set up any provider credentials in your own local environment. This guide never asks for or stores them.