@deepseek-ai/dsh-home-paths
@deepseek-ai/dsh-home-paths is a shared library inside a DeepSeek Harness profile: path resolution shared by profiles and plugins.
Currently 0.2.2-rc.3. It is not a plugin row: it has no panel to install and should not be removed on its own, because other packages are built on it.
What it is
A plugin that writes a file and the CLI that later looks for it resolve the DSH home directory the same way, so they agree on where it went.
Any plugin that stores something under $DSH_HOME should resolve it through this package instead of hard-coding a path; that is what makes the same profile work on Windows and macOS.
It arrives with a profile, not as an install
None of the 16 profile packages depends on it directly; it comes in with the plugins that declare it as a peer.
None of the 16 profile packages lists it as a dependency; it arrives with the plugins that declare it as a peer. Check your own $DSH_HOME/profiles/<name>/package.json — if a plugin that needs it is installed and it is absent, that plugin is the one to look at.
"@deepseek-ai/dsh-home-paths": "0.2.2-rc.3"
# $DSH_HOME/profiles/<name>/package.jsonWho uses it
5 community plugins declare it as a peer; each page shows what it patches.
Version and engines
npm publishes 0.2.2-rc.3 (2026-11-13); the previous publish was 0.2.2-rc.2 on 2026-11-12. Note the latest tag still points at 0.0.1-rc.3, so npm view without a version is misleading here.
Common questions
Why not just hard-code ~/.dsh in a plugin?
Because the home directory is relocatable: $DSH_HOME can point somewhere else, and on Windows the separator differs. A hard-coded path works on the machine it was written on and fails on the next one.
Which community plugins pull it in?
The five listed above, and they are the ones that persist something of their own — a cost ledger, a remote session token, a team pipeline state. A plugin with no storage peer will not ask for it.