dsh-providers-hub
One hub for coding providers: account login, multiple accounts, and switching between them.
Version 2.24.261113 of dsh-providers-hub, last published 2026-11-13; the install command and the range come from its own manifest.
Install
dsh plugin add dsh-providers-hub writes one dependency line into the profile manifest; pnpm then unpacks it under $DSH_HOME/profiles/<name>/node_modules.
dsh plugin --profile web add dsh-providers-hubCompatibility
dsh-providers-hub ships no engines.dsh entry, so nothing checks it against your CLI version at boot. Read the npm page before installing.
If two plugins fight
Holds provider accounts and switches between them. @xixka/dsh-hub covers the same ground with a different package; two account stores means one login you cannot see from the other UI.
Who made it
Author: iJetLi. Repository: https://gitee.com/iJetLi/deepseek-harness-codearts. Package page: https://www.npmjs.com/package/dsh-providers-hub.
After install
It declares @deepseek-ai/cordis as a peer and renders an account list in the settings page; after dsh plugin add dsh-providers-hub, dsh --profile web --dump-config lists the row that mounts it.
Files it touches
dsh-providers-hub routes whatever it persists through @deepseek-ai/dsh-credentials under $DSH_HOME, and its own dependency line sits in $DSH_HOME/profiles/<name>/package.json.
Removing it
Removing dsh-providers-hub is the mirror command, dsh plugin --profile web remove dsh-providers-hub; the surface goes with it, and whatever it stored under $DSH_HOME stays until you delete it.
Common questions
Does it collide with @aiwayds/dsh-llm-proxy?
For dsh-providers-hub the recommendation is @aiwayds/dsh-llm-proxy: Traffic splitting is only observable if every model call goes through the one dispatcher.
What happens when dsh upgrades?
Nothing declares a version window for dsh-providers-hub: dsh --version tells you what you are running, and no check will tell you whether dsh-providers-hub matches it.