dsh binary. Similar names are not provenance.Choose by what you need to prove.
Smallest setup. Pin the version in the command.
npx @deepseek-ai/dsh@0.1.0-rc.7 webRecord the package in a disposable manifest and lockfile.
npm install --save-exact @deepseek-ai/dsh@0.1.0-rc.7Test a named Git revision and freshly built artifacts.
pnpm install && pnpm run build && pnpm dsh webConvenient, but always prove which binary the shell selected.
command -v dsh && dsh --versionFirst read, then run.
npm view @deepseek-ai/dsh \
name version dist-tags repository.url homepage bin --json
npx @deepseek-ai/dsh@0.1.0-rc.7 web
Do not collapse three coordinates.
Path, version, package identity, or source commit.
DSH_HOME, profile manifest, bundles, and patches.
Launch directory and selected workspace realpath.
Capture the resolved graph.
npx @deepseek-ai/dsh@0.1.0-rc.7 --version
npx @deepseek-ai/dsh@0.1.0-rc.7 \
--profile web --dump-config > resolved-web.yml
Route the first failure.
Compare the requested package, shell-selected path, and reported version.
Check the Git revision, pinned pnpm, and a fresh pnpm run build.
Run an exact project-local A/B before changing the global store.
Inspect DSH_HOME and profile patches; executable installation is separate.
The CLI, profile composition, and workspace are independent. Record all three before filing an installation or startup report.
Primary evidence.
- Official run instructions
- Official CLI overview
- Official execution and profile contract
- Official rc.7 release
Keep the full installation record.
The canonical guide includes exact commands, state isolation, first-run acceptance, global-install comparison, a failure router, and a reusable reproduction template.
Read the complete guide on GitHub