What to collect before asking for dsh install help
Helpfulness depends less on how long your description is than on whether the material covers four decision points: version, logs, directory layout, and network with port. With all four, most questions resolve without a back-and-forth.
Why dsh support material decides speed
"It will not install" maps to at least six causes; material exists to eliminate possibilities, not to prove you did it right.
dsh support bundle items one and two: version, environment, log
Version information is the only way to pin down which generation of behavior you face.
- The output of
dsh --version, or a note that only npx is available; node -vandnpm -v;- Operating system and architecture;
- Install method: npx, global npm, or desktop;
- The output of
which -a dsh.
The last one is the most overlooked. It exposes duplicate installs, which is the main cause of version confusion.
When the version story is unclear, the log fills it in. Take the first error and its context, not the final line:
- Reproduce the failure once and keep the full terminal output;
- Open the logs directory in DSH_HOME and find the newest
startup-*.log; - Keep a dozen lines before the first error plus the complete stack;
- Record the exit code, usually 1;
- If the terminal mentions "Full diagnostics", follow that path.
The report is complete and the terminal is a summary. Provide both when you can, and prefer the report when you must choose. If startup failed and no log was produced, say so — that absence is itself evidence.
dsh support bundle items three and four: layout, network, port
Layout answers whether a profile initialized and where plugins went.
- Print the DSH_HOME path with
echo $DSH_HOME, defaulting to~/.dshwhen empty; - List the directory names under
profiles/; - List one level inside the target profile, looking for a package file and patches;
- Confirm whether the logs directory exists;
- Keep only names and levels.
Never send file contents, but names are clues. Settings and credentials live in those files, while a layout containing only web and no headless immediately narrows the problem.
Layout says where things sit; network and port say whether they run. These decide whether packages can be fetched and whether the service can bind:
npm config get registry, with internal addresses masked if needed;- Whether a proxy is set — yes or no is enough, not the full address;
lsof -i :3080, or whatever port you use;- The status line from
curl -I http://127.0.0.1:<port>; - One sentence on whether the registry is reachable.
Port conflicts and network failures look alike. One is a process owner, the other reachability; both need a conclusion.
One dsh collection pass and redaction
Run in this order and the output is already a bundle.
- Collect the five environment commands;
- Reproduce the failure and save the output;
- Take the newest diagnosis report;
- Print the directory layout, names only;
- Capture port and network state;
- Redact, then send.
A fixed order is what makes the bundle complete. Collecting by inspiration usually skips the port state.
Collection is not the last step. The official documentation says the report is not redacted, so this step is yours:
| Content | Action |
|---|---|
| API keys, tokens | Delete entirely, not partially masked |
| Internal hostnames and IPs | Replace with placeholders |
| Personal paths | Replace with ~ or <home> |
| Session text | Delete; keep counts only |
| Proxy addresses and accounts | Delete or replace |
Masking the middle is not redaction. Prefixes and suffixes still identify an account, especially for keys.
Read it once more after editing. Reports contain fields you did not expect, including paths inside startup arguments.
How to write a dsh help request
Complete material still needs a readable framing.
- One sentence of goal;
- The exact command you ran;
- One sentence of symptom versus expectation;
- What you already ruled out;
- The four items as attachments.
"Ruled out" saves half the round trips, because nobody repeats advice you already tested.
Keep one problem per request. One problem, one bundle.
dsh next steps
Prepare the four items before describing the problem. To triage startup yourself, read the startup decision tree. To know which document to open, read the docs map. For post-install checks, read the acceptance test. For port conflicts, read fixing dsh port conflicts.
Sources: dsh CLI reference, dsh CLI README, DeepSeek Harness docs
FAQ
When a required plugin fails, the CLI prints the plugin and stack in the terminal and writes the full report to a single startup-<timestamp>-<uuid>.log under the logs directory in DSH_HOME, then exits with status 1. The terminal message is only a summary.
No, the dsh diagnosis report is not safe to paste as-is, because the official documentation states it is not redacted and may contain configuration values or credential fragments. Review every section and remove keys, tokens, internal hostnames, and personal paths before sending.
For dsh startup failures, the paragraph around the first error is most useful: usually a dozen lines of leading context plus the complete stack. A full screen buries the signal, while only the last line is often the tail of a cascading failure.
Only names and levels, enough to show whether a profile initialized and where plugins went. Never include file contents: settings and credentials live in those files.
Related Terms
- diagnosis report
- A diagnosis report is the file the CLI writes automatically when startup fails, containing versions, platform, profile, inactive plugin states, and raw errors, and it is not redacted.— dsh CLI reference
- support bundle
- A support bundle is a small set of artifacts — environment, logs, directory layout, network and port state — that covers most triage without exposing data.— DeepSeek Harness docs
- redaction
- Redaction is the process of removing or replacing keys, tokens, hostnames, internal addresses, and personal paths before material is shared outside your machine.— dsh CLI reference
- profile
- A profile is a named assembly environment at $DSH_HOME/profiles/<name>, each holding its own dependencies and configuration.— dsh CLI README
Sources
- dsh CLI reference· deepseek-ai
- dsh CLI README· deepseek-ai
- DeepSeek Harness docs· deepseek-harness