@aiwayds/dsh-llm-proxy
A system proxy plus a traffic-splitting proxy for model calls, so one host can route several providers.
Version 0.8.1 of @aiwayds/dsh-llm-proxy, last published 2026-11-13; the install command and the range come from its own manifest.
Install
dsh plugin add @aiwayds/dsh-llm-proxy writes one dependency line into the profile manifest; pnpm then unpacks it under $DSH_HOME/profiles/<name>/node_modules.
dsh plugin --profile web add @aiwayds/dsh-llm-proxyCompatibility
@aiwayds/dsh-llm-proxy 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
Installs a process-global interceptor for outbound model calls. Any second plugin that swaps the HTTP dispatcher — another proxy, or a provider plugin with its own transport — silently bypasses it.
Who made it
Author: fan56. Repository: https://github.com/fan56/dsh-llm-proxy. Package page: https://www.npmjs.com/package/@aiwayds/dsh-llm-proxy.
After install
It declares @deepseek-ai/cordis as a peer and renders a proxy entry under model calls in the model request path; after dsh plugin add @aiwayds/dsh-llm-proxy, dsh --profile web --dump-config lists the row that mounts it.
Files it touches
@aiwayds/dsh-llm-proxy routes whatever it persists through @deepseek-ai/dsh-settings under $DSH_HOME, and its own dependency line sits in $DSH_HOME/profiles/<name>/package.json.
Removing it
Removing @aiwayds/dsh-llm-proxy is the mirror command, dsh plugin --profile web remove @aiwayds/dsh-llm-proxy; the surface goes with it, and whatever it stored under $DSH_HOME stays until you delete it.
Common questions
Does it collide with dsh-providers-hub?
@aiwayds/dsh-llm-proxy is the one to keep here: 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 @aiwayds/dsh-llm-proxy: dsh --version tells you what you are running, and no check will tell you whether @aiwayds/dsh-llm-proxy matches it.