Introduction

The design philosophy of DeepSeek Harness (DSH) is “everything is a plugin.” When developers need to manage subscription plans from multiple vendors at the same time (such as ChatGPT Codex, Claude Code, ZCode (GLM), or Qwen), configuring each provider one by one in dsh is both tedious and error-prone. The dsh-plan-bridge plugin provides a local bridging solution that maps these multiple subscription plans into dsh model groups through a single process.

What It Is

dsh-plan-bridge is a local loopback proxy process running on 127.0.0.1:8417. It does not modify dsh core files and only acts as an intermediate layer to forward requests. The plugin provides a status card in the settings page, supports one-click connection and detection, and integrates multiple vendor subscription plans into dsh’s model routing system.

Installation

Install it using the official plugin command. After installation, restart the host process.

dsh plugin --profile <name> add -w @taylorswitiger/dsh-plan-bridge

Core Features

  1. Multi-plan bridging: Supports connecting ChatGPT Codex, Claude Code, ZCode (GLM), and Qwen subscription plans to dsh.
  2. Local process: Listens for requests on 127.0.0.1:8417 and routes them by path prefix.
  3. Visual management: Provides a status card in the settings page, displaying connection status, credential availability, and error messages.
  4. Zero intrusion: Does not modify dsh core files and does not depend on runtime npm packages.
  5. Dual authentication modes: Supports both OAuth and API Key authentication.

Authentication Methods

The plugin handles different types of credential storage:
- OAuth plans: Reads credential files from vendor CLIs (such as ~/.codex/auth.json or ~/.claude/.credentials.json). The plugin is responsible for token refresh and writes updates back to the original files. Before connecting, you must first run the vendor CLI to log in.
- API Key plans: Uses the credential store in dsh settings. The plugin only passes through the Authorization header and does not store the key.

Usage Examples

After installation, the bridge listens on 127.0.0.1:8417 by default. You can test it directly over HTTP or manage plans by calling RPC methods.

  1. Health check:
GET http://127.0.0.1:8417/health
  1. RPC method call (assuming the host is running on 3080):
curl -s http://127.0.0.1:3080/dsh-plan-bridge/plans.list \
  -H 'content-type: application/json' \
  -d '{"type":"client-request","rpcId":"1","method":"plans.list","payload":{}}'
  1. Environment variable configuration (if an upstream proxy is required):
NODE_USE_ENV_PROXY=1
HTTPS_PROXY

Notes

  • Environment requirements: Requires Node.js version >= 22.19.
  • License: MIT License.
  • Permission constraints: The plugin process runs with the permissions of the current host process; it is recommended to review the source code before installation.
  • Immutability: The plugin does not modify agent-default-model, and all credential writes are performed through dsh’s credentials service.

Use Cases

Suitable for developers who need to integrate existing ChatGPT Codex Plus/Pro, Claude Pro/Max, ZCode, and Qwen subscription quotas and want to unify routing and management in DSH.

Ecosystem Background

DSH’s philosophy is “everything is a plugin.” This plugin is listed in the community directory and has no official relationship with DeepSeek or High-Flyer.