DeepSeek Harness One-Click Deployment Script (Windows)

English | 简体中文

Just 2 files to deploy DeepSeek Harness on Windows with zero dependencies — no pre-installed Node.js / Git / pnpm required. It never pollutes your system: delete the folder and it's fully uninstalled.

Quick Start

1. Put the 2 files in the same folder (avoid overly deep paths, e.g. D:\dsh)

2. Double-click setup_dsh.bat — it automatically: downloads portable Node.js → installs pnpm → fetches the dsh source → installs dependencies → performs a full build → guides you through API Key setup (first run takes about 10-30 minutes)

3. Double-click start_dsh.bat — starts the Web UI and automatically opens your browser at http://127.0.0.1:3080

For daily use, you only need step 3.

How It Works: Auto-Generated Environment, Delete the Folder to Uninstall

When the script runs, it creates an env\ virtual environment in the script folder — everything lives inside this one folder:

your-folder\
├─ setup_dsh.bat       One-click install / update / rebuild
├─ start_dsh.bat       One-click start
├─ README.md
└─ env\                ← auto-generated; deleting this folder fully uninstalls
   ├─ node\            Portable Node.js 22.19.0
   ├─ node_modules\    pnpm 11.7.0
   ├─ source\          dsh source code (master branch, built)
   │  └─ .env          API Key (generated locally, excluded via .gitignore)
   ├─ .pnpm-store\     Dependency cache (reusable offline)
   ├─ dsh-home\        All Harness data (sessions, config, plugins)
   └─ ENV.bat          Environment loader (auto-generated by setup; don't edit)

• Where the API Key lives: env\source\.env, entered during setup. dsh load order: environment variables > .env in the working directory > $DSH_HOME\.env.
• Updating dsh: re-run setup_dsh.bat — in git mode it runs git pull automatically; in zip mode it asks before re-downloading and overwriting, then installs dependencies incrementally and rebuilds.
• Modifying the source for experiments: edit files directly in env\source, then run env\node_modules\.bin\pnpm.cmd run build and double-click start_dsh.bat. CLI mode: first call env\ENV.bat, then cd env\source, then pnpm dsh --profile headless "task".
• Changing the port: start_dsh.bat <port-number>; changing the listen address: dsh web --host <address> (0.0.0.0 is rejected; you need to configure trusted hosts).
• Moving the whole folder: scripts use relative paths (%~dp0) throughout — no changes needed after copying or moving.
• Uninstalling: delete this folder (all data lives in env\).

FAQ

• Node / source download failure: the official Node source falls back to npmmirror automatically; if the GitHub zip download fails, check your network and re-run. For slow dependency installs in CN network environments, run env\node\npm.cmd config set registry https://registry.npmmirror.com first (pnpm reads npm config too), then re-run setup.
• pnpm install errors: usually network issues; see the mirror config above; re-run setup after confirming.
• Build failure: re-run once first (incremental build). If you run out of memory, set NODE_OPTIONS=--max-old-space-size=4096 as the script suggests. If you get type errors, the upstream master branch is in a mid-development state — wait a few hours and update again.
• "The source tree is not built yet" / "The web UI is not built yet": the build artifacts are missing (each package's lib bundle or apps\web\dist\index.html); re-run setup_dsh.bat to complete the build (steps already finished are skipped automatically).
• Browser doesn't open automatically: just visit http://127.0.0.1:3080 manually.
• Disk usage: source + dependencies + build artifacts take about 2-4 GB (env\.pnpm-store is the biggest chunk; deleting it is safe but makes future installs slower).

Open Source & Privacy

• This directory contains only generic scripts, no secrets. Your API Key is only ever generated locally in env\source\.env.
• This project is an independent third-party tool — a Windows one-click deployment script for deepseek-ai/deepseek-harness (MIT License). It is not an official product.
• API usage costs are billed to your own DeepSeek account.