First-session checklist
Your progress stays in this browser only. It is not sent to HarnessBase.
0 of 5 boundaries checked.
1. Start from the repository environment
DSH uses the invoking directory as the default filesystem location, but a fresh Web UI has no selected workspace. Start from the environment that owns the repository, then open the printed URL.
npx @deepseek-ai/dsh web2. Configure the model before diagnosing the composer
Open Settings → Models. For DeepSeek, enter the API key and save. The official guide says the route becomes usable immediately without restarting. Keys are write-only in the UI: settings retain a credential reference while the secret is stored in the DSH credentials file.
Watch one provider workflow without mistaking it for verification
This embedded walkthrough is the YouTube source behind the OpenRouter workflow observation. The page keeps the source, timestamps, and evidence limit beside the player so the demonstration cannot silently become an official claim.
YouTube · community observed
OpenRouter setup and model selection
Shows Settings → Models → Add provider → OpenRouter, model selection, and a reported successful response.
Boundary: Provider inventory and model availability can change. HarnessBase has not repeated this flow with a disposable OpenRouter key, so it is a visual workflow reference rather than feature verification.
Open the cited segment on YouTube ↗3. Select the workspace explicitly
Click Choose workspace, add the project directory where DSH was started, and select it. The composer remains unavailable until both a model and workspace are ready. Verify the displayed directory before allowing edits or commands.
4. Use a narrow first prompt
Summarize this repository and identify its main packages.This confirms model access, workspace reading, session creation, and output without requiring a write. If the agent asks for approval, read the exact operation and target before accepting.
5. Extend one boundary at a time
After the first task works, choose one next job. Add a plugin only after its source and permissions are understood. Add one MCP server and verify its discovered Tools before adding another. Change permission policy only when a named task requires it.
Provenance ledger
Evidence sources used on this page
- Official Official Web UI guide ↗
Model, workspace, and first-task flow.
- Official Official provider guide ↗
Provider fields, credentials, and model setup behavior.
- Direct test HarnessBase Windows lifecycle test
Retained commands, environment, HTTP readiness, process-tree memory, browser checks, version switching, profile removal, and reinstall results.
- Community Coding Shiksha OpenRouter walkthrough ↗
Visual provider and model-selection workflow. Community observed; provider success has not been reproduced by HarnessBase.