The first five minutes with dsh web: command to message
The first five minutes need five actions: start and read the log, open the printed URL, configure one provider, send a message, then stop and start again. Features can wait; if these fail, everything after them stalls.
dsh web minute 0-1: start and read the log
One command, but three things in its output matter.
- Run
npx @deepseek-ai/dsh webin a terminal; - Wait through the first download and initialization until the service announces itself;
- Read three items from the log: the address, the port, and the complete URL with its token;
- Keep the terminal open, because the service lives in that process;
- If the port is taken, change it and read the new address from the log.
The URL in the log is the entry point. Remembering only the port and not the token guarantees a rejection at the next step.
dsh web minute 1-2: open the printed URL
Authentication failures usually mean the root address was opened.
- Copy the URL from the terminal completely, from
httpto the last parameter; - Paste it into a new tab instead of refreshing an old one;
- If the page loads, the token is valid;
- Bookmark it if you like, knowing a restart may invalidate it;
- If it still fails, try a private window to rule out cache.
Reopening is not refreshing. An old tab may hold an expired token, and refreshing only repeats the failure (source).
dsh web minute 2-3: configure one provider
Configure the simplest provider first; resist tuning parameters.
- Official provider: choose it, paste the API key, pick a model, send a test message;
- Third-party gateway: enter the base URL and key, confirm the protocol and model name;
- Local model: enter the base URL and model name, and confirm the port is reachable first.
For the first run, only prove that text comes back. Leave temperature, output limits, and system prompts at defaults so there is one variable, not five.
Do not paste a key into the chat box. Configuration lives in settings; anything typed into a conversation becomes part of the transcript.
dsh web minutes 3-5: send a message, stop, start again
The first message tests both answering and saving.
- Ask the shortest possible question;
- Confirm output appears and note roughly how long the first token took;
- Open the sessions directory under DSH_HOME (default
~/.dsh); - Sort by time and confirm a new file;
- Refresh the page and confirm the session is still listed.
In the interface but not on disk means nothing was persisted. Do not install plugins yet; fix directory permissions or the DSH_HOME path.
Sending a message is not the end; the last step is to stop the service and start it cleanly once more.
Only a clean stop and a clean second start counts as working.
- Press Ctrl+C in the terminal;
- Confirm the page no longer reachable, proving the service really stopped;
- Run the start command again;
- Copy the new tokenized URL and open it;
- Confirm the previous session is still listed.
The second start is the acceptance test for the first. One successful start may be luck; a second one means the configuration is stable.
dsh web five-minute checklist and common blockers
All five pass before exploring features.
| Time | Action | Passing |
|---|---|---|
| 0-1 min | Start | Log shows an address and token |
| 1-2 min | Open | Tokenized URL loads |
| 2-3 min | Provider | A test message returns output |
| 3-4 min | Message | Answer plus a new file under sessions |
| 4-5 min | Restart | Stops, starts, session survives |
Fix any failed item before moving on. Continuing with an open failure makes later errors impossible to attribute.
Whatever failed in the checklist usually lands in one of these four blockers.
Most first-run failures are one of these.
- Opening the root address: auth is requested; copy the complete URL instead;
- Port already in use: change the port and use the new address from the log;
- No provider configured: the page loads but messages fail; configure a provider in settings;
- Closing the terminal: the service stops by design; start it again and copy the new token.
None of these needs a reinstall. Reinstalling fixes missing programs, not addresses, ports, or configuration.
dsh web next steps
Once it works, add features and acceptance checks. For what each UI area does, read using the dsh web UI. For tokens and auth, read web authentication required. For startup flags, read the npx startup command. For a full checkup, read the ten-minute acceptance test.
Sources: dsh CLI reference, DeepSeek Harness docs, DeepSeek API docs
FAQ
The usual cause is opening the dsh web root URL instead of the URL printed in the log. Copy the complete URL the process announces, including any token parameter, into a fresh tab. Refreshing an old tab keeps resending a stale value.
The dsh web access URL does not necessarily stay valid after a restart. The announced URL can change between runs, so copy the new one each time. Bookmarking the old address is fine only if you remember to update it after a restart.
The dsh web install is usually fine; no provider is configured. The interface can open with no model behind it. Configure one provider in settings, keep all other parameters at defaults, and send a minimal message before touching anything else.
Check the sessions directory under DSH_HOME, default ~/.dsh. After a message completes, sort by modification time; a new file means it persisted. Visible in the UI but absent on disk means the data directory is wrong or unwritable.
Related Terms
- access URL
- The access URL is the address announced when dsh web starts, including its port and any token parameter, and it is the only supported entry into the interface.— dsh CLI reference
- provider
- A provider is a configured source of model access, holding an endpoint, credentials, and a model name that the session uses for requests.— DeepSeek API docs
- DSH_HOME
- DSH_HOME is the data root for DeepSeek Harness, defaulting to ~/.dsh, where sessions, settings, profiles, and credentials live.— DeepSeek Harness docs
- time to first token
- Time to first token is the delay before the first output fragment arrives, a quick baseline for later performance comparisons.— DeepSeek Harness docs
Sources
- dsh CLI reference· deepseek-ai
- DeepSeek Harness docs· deepseek-harness
- DeepSeek API docs· DeepSeek