DSH Error Fix Center
Paste the exact terminal error into search to see the fastest next step here, then open the matching page. Each page targets one primary error code or symptom.
On this page
Each error page starts with the exact error text, then gives the fast fix, cause, source trace, steps and verification. Search with raw strings such as EADDRINUSE, MISSING_CREDENTIAL, UNKNOWN_MODEL, 401 or npm.ps1.
You can paste a full terminal error line. Search runs locally in your browser, and the text you enter is not uploaded.
MISSING_CREDENTIAL Error
Save a credential for the provider used by the current DSH session, then select a valid model and retry.
UNKNOWN_MODEL Error
Select a model ID that actually exists under the configured provider, or add that model before retrying.
401 Authentication Failed
Check the key, provider Base URL and any environment-based credential, then test model discovery separately from chat.
EADDRINUSE: address already in use 127.0.0.1:3080
Identify the process using port 3080 or a Windows reserved-port conflict, then stop only a confirmed stale process or use another port.
127.0.0.1:3080 Not Opening
Check whether DSH is running locally or on a remote server, then open the exact printed URL or create an SSH port forward.
'node' Is Not Recognized
Install a supported Node.js version, reopen the terminal to refresh PATH, and verify Node before starting DSH.
npm / npx Is Not Recognized
Repair the Node.js installation or PATH until node, npm and npx all work in the same terminal.
npm.ps1 Cannot Be Loaded
Use the Windows .cmd shims without changing policy, or review a CurrentUser PowerShell policy change when your environment permits it.
Browser Did Not Open Automatically
Open the printed local URL manually; automatic browser launch is optional, and SSH sessions require port forwarding.
Select Model / Input Box Disabled
Complete the three required setup items: save a provider credential, choose a workspace and select a model.
Workspace Permission Denied
Use a small user-owned test folder, verify normal read/write access outside DSH and review the active permission setting.
GitHub community error cases
Explore 11 cases from 12 original reports: Desktop startup, plugin crashes and subagent authentication failures, with version-specific evidence.
Open community cases →
Diagnose in this order
- 01
Copy the full error
Keep the last useful terminal error, its code and the exact command you ran. Do not reduce the report to only “it does not open.”
- 02
Match the exact error
Match the error code or raw phrase first, such as EADDRINUSE, MISSING_CREDENTIAL, UNKNOWN_MODEL or npm.ps1 cannot be loaded.
- 03
Change one thing at a time
Change one setting, test again, and only then continue. This shows which action actually fixed the problem.
- 04
Run one small test
Use a harmless task in a small test folder before trying a production repository, an entire home directory or sensitive files.
What to do when there is no match
Open the full troubleshooting guide and record the operating system, node --version, DSH version, launch command and complete error. Remove API keys, private repository names, usernames and sensitive paths before posting upstream.