Install Node.js
Use a currently supported Node.js release that includes npm and npx.
DeepSeek Harness (DSH) is an open-source agent harness: connect a model provider, work with local files, and add plugins and MCP. Start with installation, or find the fix for your exact error.
Use the community-maintained desktop wrapper to manage the local Harness process in a dedicated window. Review compatibility and safety notes before downloading.
See Desktop compatibility and setup →Third-party desktop app · Community-maintained, not an official DeepSeek product. The app does not include API credit.
Run the official npm quick-start directly from this page. Copy the command here; use the full operating-system guide if any step fails.
Use a currently supported Node.js release that includes npm and npx.
Run the official npm quick-start command and keep the terminal open.
npx @deepseek-ai/dsh webOpen Settings → Models, save your provider credential, choose a disposable test folder and run one small task.
DSH is the open-source agent harness around a model: it connects model selection, sessions, tools, workspace access, approvals and plugins into an executable workflow.
A model produces model output. DSH supplies the runtime around it: a selected provider and model, a workspace, session history, tool execution, approval boundaries and plugin-composed capabilities.
Read the DSH overview →Claude Code is a Claude-centered coding agent product. DSH is positioned as a plugin-first harness you can reshape across providers, tools, Web UI surfaces, MCP, skills, subagents and workflows.
Compare agent workflows →Choose the one option that matches your situation now.
Choose your operating system, check Node.js, start the local Web UI and run one small test task.
Open beginner setup →Paste or search the exact error, then follow commands written for your operating system.
Search error fixes →See whether an extension is official or third-party, where it appears after installation and what code may run during setup.
Explore extensions →Paste the exact terminal error below. The matching result expands the fastest next step here, with a command to copy when one is available.
You can paste a full terminal error line. Search runs locally in your browser, and the text you enter is not uploaded.
Save a credential for the provider used by the current DSH session, then select a valid model and retry.
Select a model ID that actually exists under the configured provider, or add that model before retrying.
Check the key, provider Base URL and any environment-based credential, then test model discovery separately from chat.
Identify the process using port 3080 or a Windows reserved-port conflict, then stop only a confirmed stale process or use another port.
Check whether DSH is running locally or on a remote server, then open the exact printed URL or create an SSH port forward.
Install a supported Node.js version, reopen the terminal to refresh PATH, and verify Node before starting DSH.
Repair the Node.js installation or PATH until node, npm and npx all work in the same terminal.
Choose your system so the commands and troubleshooting match your machine.
Windows 10/11 setup with Node.js, PowerShell and the official npx quick-start, plus npm.ps1 and port 3080 troubleshooting.
Open Windows installation guide →Install Node.js, launch the local DSH Web UI with npx, configure a model and run your first workspace task on Intel or Apple silicon Macs.
Open macOS installation guide →Use nvm or your existing Node.js environment, launch DSH with npx, and handle local versus remote-server access to the Web UI.
Open Linux installation guide →Add an API credential, choose a test folder, select a model, review approvals and confirm the result on disk.
Official master identifies 0.1.2-alpha.5 at 49a606b.
Open version sources →See where DSH differs from Hermes, Claude Code, Codex and OpenCode before choosing a workflow.
Open agent comparison →Official and third-party describe the source. Install scripts, requested access and review records must still be checked separately.
Review plugin policy →