AI Agent Hub
Back to plugins
🧰

dsh-plan-bridge

Web Tools Updated 2026.09.04

Run the following command in DeepSeek Harness:

dsh plugin install TaylorSwitiger/dsh-plan-bridge

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

Run dsh plugin install TaylorSwitiger/dsh-plan-bridge in the DeepSeek Harness terminal to install this multi-plan bridging plugin. Source repository: https://github.com/TaylorSwitiger/dsh-plan-bridge .

About this plugin

You likely hold multiple LLM subscriptions—Codex Plus/Pro, Claude Pro/Max, ZCode, Qwen—each with its own CLI, credential file, and calling convention. Pulling all of them into DeepSeek Harness (dsh) model groups normally means hand-editing provider blocks, managing token refresh, and juggling credential formats across vendors.

dsh-plan-bridge runs a single local loopback process (default 127.0.0.1:8417) that routes by path prefix and serves every subscription at once. OAuth plans (Codex, Claude) reuse the vendor CLI credential file and auto-refresh tokens back into it; API-key plans (ZCode, Qwen) keep the key in dsh's credential store—the bridge only forwards the Authorization header and never persists the key to its own files. The Settings > Plan Access card gives per-plan status with one-click provisioning (idempotent: validate credentials, write the provider section, add a placeholder credential) and clean teardown. No dsh core files are touched and agent-default-model is never modified.

Built for dsh users who already pay for multiple LLM subscriptions and want a single workspace with per-group model switching. Zero runtime npm dependencies, no bundler required—install, restart the host, and you are live. Adding a new vendor is one adapter file plus one registry line.

Use Cases

  • Holding Codex, Claude, ZCode, and Qwen subscriptions simultaneously and wanting per-group model switching in dsh
  • Preferring one-click provisioning and clean teardown over hand-editing provider blocks and token refresh per vendor
  • Adding a new LLM plan with a single adapter file plus one registry line—routing and UI card go live automatically

Best For

  • dsh users with multiple LLM subscriptions seeking a unified workspace
  • Plugin adopters who value zero runtime dependencies and zero core modifications
  • Developers needing both OAuth auto-refresh and API-key pass-through modes in one stack