AI Agent Hub
Back to plugins
dsh-router preview

dsh-router

Client Updated 2026.09.05

Run the following command in DeepSeek Harness:

dsh plugin install CARVIN94/dsh-router

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install CARVIN94/dsh-router in DeepSeek Harness to install this plugin, source at https://github.com/CARVIN94/dsh-router

About this plugin

Routing multiple AI providers inside DSH used to mean spinning up a separate 9router gateway, babysitting an extra port, and shuffling configs back and forth. dsh-router folds that routing layer into a native DSH web plugin that boots and shuts down with dsh web, exposes a standard OpenAI-compatible endpoint at localhost:3080/v1, and parks its entire management UI under Settings → Router—no extra process, no extra port.

The core design principle is to write policy once: combo fallback chains, account-pool management (round-robin, cooldown, disable, health probe), credentials in a single SQLite database, and model fetching with a 60-second TTL are all handled by the core. A supplier module only translates the upstream protocol into OpenAI shape and reports single-call success or failure; account rotation, persistence, and points are the core's job, so no plugin grows its own inconsistent copy of that logic. The panel ships a usage dashboard (trend chart, top list, recent requests), supplier cards (link pool, one-click check-in, per-model enable/disable and probe), combo editing, and API key management—all ready to use out of the box.

It is built for users who already run OpenAI-compatible tools like Claude Code or Cline on DSH and want unified multi-provider access without maintaining a standalone gateway, and for developers who want to publish suppliers as DSH plugins that share the same routing and credential stack.

Screenshots

Use Cases

  • Unify multiple AI providers in DSH without running a standalone gateway
  • Auto-fallback from free-tier to paid suppliers via combo chains
  • Serve a local OpenAI-compatible endpoint for tools like Claude Code or Cline

Best For

  • Developers already using DSH who want multi-provider access
  • Engineers looking to reduce extra processes in their local AI toolchain
  • Developers who want to publish new supplier integrations as DSH plugins