CLI integration

Verify the desktop-provided dsh command and understand PATH and shell configuration changes.

Release builds enable CLI integration by default. A lightweight dsh shim starts the Harness CLI using compatible system Node.js or the managed runtime.

Verify the command

After installation or setting changes, close old terminals and run this in a new terminal process:

dsh --help

Check which command your shell resolves:

PowerShell

Get-Command dsh

macOS / Linux

command -v dsh

What changes

Platform	Shim directory	Registration
Windows	%LOCALAPPDATA%\deepseek-harness\bin	Changes user-level PATH, not system-level PATH
macOS / Linux	~/.local/bin	Adds marked PATH blocks to managed shell startup files

Unix integration does not rewrite the entire shell configuration, but it does edit relevant startup files. Disabling integration removes the managed blocks. A detected user-installed command with the same name is preserved; shell resolution determines which command runs.

The shim prefers supported system Node.js, then falls back to the app-managed runtime. pnpm similarly prefers the user command before the managed version.

Command not found

1. Confirm CLI integration is enabled in desktop Configuration → Application and check registration status.
2. Open a new terminal process and confirm the shim directory is in PATH.
3. Check whether another installed dsh is selected; follow the interface prompts to repair integration.
4. If it still fails, preserve the error and see Troubleshooting.

Debug builds do not register or remove user PATH entries or overwrite the release dsh shim. They may prepare a pnpm shim for internal operations, so a development launch does not imply release CLI integration is enabled.