Introduction

When integrating WorkBuddy, Trae, and Qoder for model inference in DeepSeek Harness (DSH), the common approach is to install three separate connectors, each maintaining its own accounts and model list. As accounts grow, switching channels, aligning model names, and rotating accounts after quota exhaustion or rate limiting often require toggling back and forth across multiple configuration pages.

The following introduces the community plugin dsh-multi-router (maintained by AndroidSix, categorized under “Model Inference”). It consolidates authentication, model discovery, and chat transport for the three providers into a single plugin, using an account pool and routing rules for unified scheduling, with support for quota and rotation policies.

What Is This

dsh-multi-router is a multi-account routing plugin for DSH: it provides a WorkBuddy / Trae / Qoder account pool, model routing, and quota rotation. According to the plugin description, it does not depend on the original three standalone DSH connectors at runtime; the related capabilities for all three providers are bundled with the package.

Community directories such as SkillHub have no official affiliation with DeepSeek / Hithink RoyalFlush; refer to the repository documentation and license before installation.

Core Features

The following capabilities are derived from the plugin’s public documentation (README content synced to the DSH Directory) and are provided as a summary.

Unified Three-Provider Channels and Centralized Routing

It ships with built-in providers such as WorkBuddy, Trae (including CN / Global editions), and Qoder, performing centralized routing through the multi-router channel. On first enablement, it can automatically detect locally logged-in WorkBuddy / Trae accounts; Qoder requires a PAT or reading credentials saved by the legacy connector.

Account Pool and Switching

Each account maintains independent credentials and caches. On upstream 4xx responses (including quota exhaustion, rate limiting, permission issues, etc.), the plugin can switch to the next account according to rules; it supports strategy options such as failover, weighted round-robin, token quota-based, and credit consumption-based, with configurable options including preferring accounts with near-expiry credits, credit balancing, and discount-based sorting.

Panel and Statistics

The DSH plugin configuration page allows you to manage overall usage, token details, accounts and login, routing rules, model management, credit check-in, an optional OpenAI-compatible API service, configuration migration, and more. Usage data and details are stored locally in the data directory; full prompt text is not retained (subject to the documentation’s description).

Compatibility with Legacy Connectors

The documentation requires that the three original standalone connectors for WorkBuddy / Trae / Qoder be disabled in DSH before the first installation (disabled only, no need to uninstall), to avoid provider name conflicts.

Installation and Enablement

Prefer the official npm package. In DSH, go to “Plugins → Install Plugin” and enter the package name dsh-multi-router; the command line requires using a name consistent with your actual profile (desktop / web are documentation examples only).

# Desktop profile
dsh plugin --profile desktop add dsh-multi-router

# Web profile
dsh plugin --profile web add dsh-multi-router

You can also fill in the GitHub repository address https://github.com/AndroidSix/dsh-multi-router on the plugin page, or use the GitHub dependency format via CLI:

dsh plugin --profile desktop add github:AndroidSix/dsh-multi-router

Per the documentation: it fetches the main branch by default, and the package already contains the compiled lib/, so no cloning or building is needed on the installation side. npm users can update via:

dsh plugin --profile desktop update dsh-multi-router

Compatibility notes (from the documentation): DSH Desktop / Web 0.2.1-rc.2 (compatible with 0.2.0-rc.2), Node.js ^22.19.0 or >=24.

Typical Usage

1. Use the Panel After Enablement

After installing and enabling the plugin in DSH, open the Plugins → dsh-multi-router configuration page: verify the account pool, edit routing rules as needed, and select the unified routing channel or exposed models in the DSH model selector.

2. Add Accounts via CLI (Optional)

Under the installed plugin package directory, you can use the bundled CLI to manually add accounts (replace the paths with real local files):

node lib/cli.js add --id wb1 --provider workbuddy --source '/path/workbuddy-desktop.info'
node lib/cli.js add --id tr1 --provider trae --edition cn --source '/path/Trae CN/User/globalStorage/storage.json'
node lib/cli.js add --id qd1 --provider qoder --source '/path/account-pat.txt'

Check status and model examples:

node lib/cli.js status
node lib/cli.js models --id wb1

3. Expose an OpenAI-Compatible API (Optional)

After enabling the API service on the panel and generating a key, the documentation’s local invocation example is:

curl http://127.0.0.1:8787/v1/chat/completions \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"model":"deepseek-v4.1-flash","messages":[{"role":"user","content":"你好"}],"stream":true}'

Use Cases and Considerations

Who it’s for: Developers who are already using or plan to use WorkBuddy, Trae, and Qoder in DSH, and want a unified account pool and routing rules for model inference, account switching, and usage statistics.

Permissions and security: DSH plugins run with the permissions of the current dsh process, capable of reading and writing local configuration, parsing client login state, and accessing the network. Before installation, you should read the source code, DISCLAIMER.md, and the license (the documentation mentions MIT upstream and THIRD_PARTY_NOTICES.md), and understand the plugin’s statement: it is for personal learning and research only, has no affiliation with WorkBuddy / Trae / Qoder / DeepSeek officially, and does not bundle accounts; parsing local login state or calling undocumented APIs may violate upstream terms of service.

Compliance and expectations: Multi-account rotation is a scheduling strategy and does not increase the total quota granted by upstream; platform balances, rate limits, and risk control remain subject to each service provider’s rules.

Conclusion

dsh-multi-router consolidates the three provider channels into a single plugin, reducing the operational overhead of maintaining multiple connectors through an account pool and configurable routing. For installation commands, versions, and a full description of capabilities, refer to the community directory page and the GitHub repository: