Run a First Task in the DSH Web UI
Get past the first-run setup gates, choose a test workspace and model, make one controlled change and verify it on disk.
On this page
DSH can work with files and commands in the selected workspace. Do not begin with an important repository or a folder containing secrets.
Start the DSH Web UI
npx @deepseek-ai/dsh webLeave the process running and open the address it prints. The default is http://127.0.0.1:3080.
DSH uses the directory where you start the process as its initial filesystem location, but that directory is not automatically selected as the Web UI workspace.
When DSH inherits an SSH connection, the current CLI intentionally suppresses automatic browser launch and still prints the host URL. Use your SSH client/editor's port-forwarding path. Do not copy old tutorials that use --host 0.0.0.0; the current shipped Web alias explicitly does not support that value yet.
Before the composer works: three first-run checks
1. Provider credential
Save a working provider credential under Settings → Models. Provider changes apply to the next request; the server does not need a restart.
2. Workspace
A fresh Web UI has no selected workspace even if you launched DSH from inside the project directory. Add and select the directory explicitly.
3. Model
Select a currently configured model. If a saved default points to a deleted provider, the composer shows Select model and blocks input.
If the page opens but feels “stuck,” check these three states before reinstalling Node or restarting the computer.
Choose a test workspace
Click Choose workspace, add a disposable folder and select it. The composer is unavailable until a workspace is selected.
If you launched DSH from C:\project or ~/project, that only gives the process an initial filesystem location. The Web UI still requires an explicit workspace selection.
Select a configured model
Open the model picker and choose a model from the provider you configured in Settings → Models.
Selecting a model makes it the default for new sessions. An existing session that already sent a request keeps the model recorded in its own log.
Start with a repository tour
Before asking DSH to change a project, ask it to read the workspace. This is the first task in the official Web UI guide:
Compare the response with the actual top-level folders and package files. A useful first session teaches you where the model is accurate and where it needs a more specific question.
Make a read-only architecture map
Once the repository tour looks accurate, use a bounded follow-up:
Read the Mermaid text before rendering it. Treat it as a review aid, not a substitute for opening the referenced files.
Make one controlled change
Start with a change that is easy to inspect and undo:
Read approval requests
If DSH asks for approval, read the operation, path and command before accepting it. Reject an unexpected or destructive action.
Verify the file yourself
Open the workspace outside DSH. Confirm that README.md exists and contains the requested text.
Work in a bounded loop
State the scope
Name the workspace, allowed files and intended output before a change task starts.
Read approvals
Do not approve a command or file operation you do not understand.
Verify independently
Open changed files and run the relevant check outside the chat response.
Startup or port error? Open error-driven troubleshooting →