Home›Error Fixes

Browser Did Not Open Automatically

Fix the browser not opening automatically by using the Web UI URL printed in the terminal and forwarding the port first when DSH runs over SSH.

On this page

First, match Browser did not open automatically

This page targets Browser did not open automatically. The full message can contain a few extra words on different operating systems or Node.js versions, but the core error code or phrase should match.

Browser did not open automatically

browser did not open

web browser did not launch

DSH browser not opening

When searching or asking for help, copy the full error and remove API keys, private repository names, usernames and sensitive paths.

Fast fix: Browser did not open automatically

If the terminal says DSH is ready, copy its printed URL into a browser on the same computer. When DSH runs through SSH, create a port forward first. Use --no-open only when you intentionally do not want DSH to launch a browser.

What Browser did not open automatically means

The DSH Web server can be healthy even when the operating system does not open a browser window.

Common causes of Browser did not open automatically

The default-browser handoff failed.
DSH is running through SSH or in a headless environment.
Desktop policy blocked automatic browser launch.
DSH was started with --no-open.

Source trace for Browser did not open automatically

These links are pinned to the 0.1.2-alpha.5 / 49a606b snapshot used for this page. They help separate Browser did not open automatically from failures produced by Node.js, PowerShell, the operating-system network stack or filesystem permissions.

Browser launcher implementationThe Web bundle contains a dedicated openBrowser() launcher. Browser launch is a convenience step after the server starts, so failure to open a window does not by itself mean the Web server failed.Official quick startThe README says local launches open the default browser, while SSH launches only print the host URL; --no-open is also supported.

Fix Browser did not open automatically

01
Check that DSH is ready
Look for the final Web UI URL in the terminal and confirm that no startup error appeared after it.
02
Open the URL manually on the same computer
Copy the exact printed address into your browser. Keep the terminal open while using DSH.
03
Forward the port for SSH
Run this on your own computer, keep the SSH connection open, and then visit http://127.0.0.1:3080 locally.
ssh -L 3080:127.0.0.1:3080 user@server
04
Disable automatic opening only when intended
This supported flag runs the server and prints the URL without trying to open a browser.
npx @deepseek-ai/dsh web --no-open

Verify Browser did not open automatically is fixed

The manually opened URL loads DSH.
The terminal process remains active while the Web UI is in use.
For SSH, the port-forwarding connection remains open.

What to avoid

Do not treat a missing browser window as a server failure before checking the printed URL.
Do not expose the service directly to the public Internet for convenience.