Before starting
- Use a supported Node.js environment and a project folder that is safe to inspect.
- Do not begin in a directory containing secrets or files you are unwilling to change.
- Keep the Web UI on its default loopback address rather than exposing it to a local network.
- Have the API credential for the model provider you intend to configure.
Launch the official Web UI
mkdir -p "$HOME/.dsh-themes/runtimes" &&
git clone --depth 1 --branch dsh-v0.1.3-alpha.1 https://github.com/deepseek-ai/deepseek-harness.git "$HOME/.dsh-themes/runtimes/0.1.3-alpha.1" &&
cd "$HOME/.dsh-themes/runtimes/0.1.3-alpha.1" &&
test "$(git rev-parse HEAD)" = "d347e703908d0406b7a7ef80e3a0e594d86b2215" &&
corepack pnpm install --frozen-lockfile &&
corepack pnpm run build:official &&
corepack pnpm dsh webComplete one small, observable task
- 01
Open the printed loopback address
The default is a browser UI on port 3080. Use the address printed by the process and keep the terminal running.
- 02
Configure a model
Open Settings and add the required provider credential. Do not paste credentials into a conversation or project file.
- 03
Choose a disposable workspace
Create a separate disposable practice project, or choose your own target project, then add and select that directory. Keep the fixed official Harness source directory as the runtime; do not select it as the Agent’s editing workspace. The composer becomes available after a workspace is selected.
- 04
Ask for a read-only first task
Start by asking the Agent to summarize the repository and identify its main packages. Review what it reads before requesting edits.
- 05
Read every approval prompt
Check the command, path, and intended effect. Reject an operation that reaches outside the selected workspace or does more than the task requires.
After the first run
Complete your first small task
After the fixed source build opens, configure a model and explicitly select your project. Ask for a README correction, inspect the diff, and verify that reopening the session preserves the conversation.
Check my Node.js and pnpm versions, build DeepSeek Harness 0.1.3-alpha.1 from commit d347e703908d0406b7a7ef80e3a0e594d86b2215, and start the Web UI. Ask me to enter my own model credentials in settings; do not print or invent them.Read the primary documentation
Common questions
Before you make a change
Answers about formats, compatibility, evidence, and rollback.
What does this guide verify?
This guide covers: Exact Alpha source-build launch; Official Web UI guide; Loopback and workspace safety boundary
What should I do first?
Use the official path for a first look, but keep the workspace disposable and the server on loopback. Exploring DSH and authorizing a verified theme are two different operations.
Which boundary matters most?
Use Node.js 24 (the repository supports ^22.19.0 or >=24.0.0) and Corepack. Corepack selects the repository’s pnpm 11.7.0 for the official build; subprocesses may use a different pnpm version. As of September 6, 2026, the exact Alpha npm package and release binaries are unavailable. The tested source build below uses a separate directory under $HOME/.dsh-themes/runtimes, outside this website or any ancestor directory containing node_modules. This prevents unrelated React dependencies from being resolved. Keep the source directory and its build output: the launcher needs them. After startup, choose a workspace and configure your model in Settings → Models.
Why does the composer stay unavailable?
A fresh Web UI has no selected workspace. Add and select the project directory, and confirm that a model is configured under Settings → Models.
Continue learning
Continue from the verified evidence
Compare published artifacts or return to the installation documentation.