Introduction¶

The plugin ecosystem for DeepSeek Harness (DSH) emphasizes feature extension and flexible integration. During development or use, you may often encounter situations where a single account’s API quota is exhausted or rate-limited, requiring a quick account switch or connection to a new resource pool. This plugin is designed to solve that problem. It does not depend on separate API keys; instead, it directly reads the locally logged-in states of WorkBuddy, Trae, and Qoder desktop applications, converts them into Providers available to DSH, and automatically switches when resources are insufficient.

What Is This¶

WTQ Account Pool is a DeepSeek Harness plugin. Its core function is to integrate accounts from the three desktop applications that are logged in on the local machine into DSH, and to provide on-demand allocation and automatic switching. The plugin is maintained by chengzhi-c and uses the MIT license. It obtains tokens by reading local login files and does not initiate additional OAuth authorization, simplifying the account onboarding process.

Core Features¶

1. Reuse Local Logins
   The plugin only reads the saved login files of the WorkBuddy, Trae, and Qoder desktop applications. It does not write login state and does not initiate OAuth authorization. This means it leverages the user’s existing login credentials.

2. Region Grouping and Provider Registration
   Models are grouped by region, and each vendor is registered as a separate Provider. Domestic and international accounts are grouped separately and can be enabled at the same time.

3. Account Distribution Strategies
   Accounts are distributed based on vendor-specific strategies:

   • WorkBuddy: Supports priority use, round-robin, expiring-soon credits priority, and session-pinned accounts. When rate limit or quota exhaustion occurs, it automatically switches accounts.
   • Trae, Qoder: Supports round-robin and expiring-soon credits priority.

4. Panel and Connection Check
   Provides a settings panel where you can view account status, pool status, selected models, and connection check results. Supports modifying model attributes such as display name, context window, and output limit.

5. Credits Display in the Input Box
   When the showComposerPoints setting is enabled, the input box displays the account balance currently used by the model. Click it to view the accounts in that group and switch between them.

Installation and Enablement¶

The plugin is distributed as a .tgz package. Before installation, you must run the build command in the source directory to generate the dsh-wtq-pool-1.0.2.tgz file, and then install it through the DSH CLI.

1. Build in the source directory:

    pnpm install && pnpm run build && npm pack --pack-destination dist

2. Run the installation command in PowerShell (replace desktop with the actual profile name):

    $package = (Resolve-Path .\dist\dsh-wtq-pool-1.0.2.tgz).Path
    dsh plugin --profile desktop add $package

After installation, go to the “Plugins” page in the DSH sidebar and click the dsh-wtq-pool card to open the full settings panel. If the model groups do not appear, restart dsh.

Typical Usage¶

1. Account Detection
   Log in to the WorkBuddy, Trae, and Qoder desktop applications, and then click “Redetect Accounts” in the plugin panel.

2. Configure Models and Strategies
   In the panel, select the models you want to expose for each region, and modify settings such as display name and context window. On the “Account Pool” page, configure the distribution strategy; for example, WorkBuddy can use “Priority Use” or “Expiring-Soon Credits Priority”.

3. Use Input Box Credits
   Enable showComposerPoints in the settings. In the conversation input area, the current model displays the account credits it is using. Click to view and switch accounts.

Use Cases and Notes¶

• Use Cases: Users who have installed and logged in to the WorkBuddy, Trae, or Qoder desktop applications locally and want to use existing account quotas, or who need to handle rate limiting on a single account.
• Security and Permissions:
  • The plugin only reads local login files and does not write state back.
  • Tokens are used only within the plugin process and sent to the corresponding vendor APIs.
  • The gateway listens only on 127.0.0.1, and panel resources and RPC only accept loopback peers; therefore, remote browsers cannot directly use the panel.
  • The plugin does not send telemetry data.
• Notes: The plugin does not directly manage or delete host session records. Other processes on the same machine can call these interfaces through loopback endpoints and thereby consume the quotas of logged-in accounts.