Requirements for dsh-xdpool
DeepSeek Harness loads dsh-xdpool in a profile such as desktop, web or dsh-tui. The README states compatibility with host 0.1.1-rc.2 through the 0.1.x series and 0.2.0-rc.2. A WorkBuddy desktop App must be installed and signed in. Additional accounts are discovered after signing into them in that App.
Configuring dsh-xdpool
The settings panel provides four account allocation modes:
| Mode |
Behaviour |
priority |
Uses one account until it cannot continue. |
round-robin |
Rotates through accounts in order. |
balanced |
Selects randomly, favouring accounts that have been idle longer. |
sticky |
Keeps one account for a conversation and changes account for a new conversation. |
Each account can also have a points-retention threshold; accounts below that balance are not assigned work. Aggregate channels are disabled by default and become available when an API key is supplied. The README does not specify standalone configuration key names for these settings.
Commands and controls in DeepSeek Harness
DeepSeek Harness exposes the plugin through the XD Pool settings tab. The documented controls are 重新检测账号 (recheck accounts), 清除所有冷却 (clear all cooldowns) and 每日签到 (daily sign-in), plus per-account sign-in controls. Credit automation can run on its schedule or through 立即运行 (run now). The README documents these as panel actions rather than CLI command names.
How dsh-xdpool behaves
A 429 places an account into cooldown; requests use another healthy account and wait only when all accounts are cooling down. Domestic credentials use copilot.tencent.com, while international credentials using the workbuddy.ai login domain use www.workbuddy.ai. Persistent data is stored in ~/.dsh/.xdpool. On startup, the plugin copies data from ~/.dsh/.workbuddy-xdpool without deleting the old directory, preserving API keys, ignored accounts, pins and logs.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub