linziyanleo/dsh-custom-provider

Registers static provider routes and model catalogs in DSH from the Web settings UI or settings.yaml, over three wire protocols.

Handles the case a base URL and an API key do not cover: a model endpoint needs its wire protocol chosen, its catalog known in advance, its capacities declared, and its reasoning or message-replay request fields mapped per provider. All of that becomes a provider route DSH can use directly. Configuration is available two ways — a bilingual Web settings page for adding, editing and removing providers, and settings.yaml for keeping it in version control. Per route you set the protocol and base URL, provider-level defaults, and then per-model entries with model ID, display name, context window and maximum output; capacity inputs accept integers or K/M suffixes such as 200K or 1m. Advanced fields stay collapsed until a model needs custom reasoning-effort mappings, and Chat Completions routes additionally expose request-compatibility overrides. Credentials are handled the way the rest of DSH handles them — the API key field is write-only and stores the value through the DSH credentials service rather than in the settings file.

Models & Providers ★ 1
View on GitHub ↗

Install

npx @deepseek-ai/dsh plugin --profile web add @linziyanleo/dsh-custom-provider

The README's Installation line, which goes through npx so it works without a global dsh. It follows with npx @deepseek-ai/dsh --profile web --dump-config to confirm the route landed, and says to pin a version for reproducible installs — @linziyanleo/dsh-custom-provider@0.1.1 is the README's own example. Removal is the same command with remove.

Compatibility

Node.js ^22.19.0 or >=24.0.0, with 22.19.0 named as the minimum verified version, and DSH 0.1.0-rc.7 compatible packages — the README defers the complete contract to peerDependencies in package.json rather than restating it. Each route selects one of three wire protocols: OpenAI Chat Completions, OpenAI Responses or Anthropic Messages. Configured models appear in DSH's native model picker and stay inside its standard streaming, tool-call, usage, finish-reason, cancellation and reasoning-effort flows, which is the reason to configure a route here instead of patching the harness. The README also carries a security and lifecycle section and an explicit current-scope section, so what it does not cover is stated rather than implied.

Details

Alternatives

deskomor/dsh-sub-providers · minglu6/dsh-provider-qoder · MoFeng2223/dsh-claude-provider

More plugins in Models & Providers

Browse more in Models & Providers

Guides for Models & Providers plugins