# dsh-workbuddy-connect-next
**The maintained successor of corrinehu/dsh-workbuddy-connect: dashboard UI, multi-account rotation and credit in the sidebar, bringing WorkBuddy desktop-app models into DeepSeek Harness.**
[](https://github.com/yoyo636/dsh-workbuddy-connect-next)
[](https://www.typescriptlang.org/)
[](https://github.com/yoyo636/dsh-workbuddy-connect-next)
[](https://github.com/yoyo636/dsh-workbuddy-connect-next)
[](./LICENSE)
[](https://github.com/yoyo636/dsh-workbuddy-connect-next/releases)
[](https://github.com/yoyo636/dsh-workbuddy-connect-next/stargazers)
[](https://github.com/yoyo636/dsh-workbuddy-connect-next)
[](https://github.com/yoyo636/dsh-workbuddy-connect-next/graphs/contributors)
[Issues](https://github.com/yoyo636/dsh-workbuddy-connect-next/issues) • [Changelog](CHANGELOG.md) • [English](README.en.md) / [中文](README.md)
---
> ## ⚠️ Read this first: upstream is tightening, and it can break at any time
>
> **Since 2026-10-20 the WorkBuddy chat gateway enforces channel verification against third-party clients.** This plugin — and every other third-party integration — can be refused outright.
>
> - Typical failure: `400 / code 11128 / Illegal API invocation from an unapproved channel`, surfaced to users as 「请求被拦截，请重新发送」 / 「这次调用没通过渠道校验，可能不是官方客户端发出的」.
> - The checks keep growing. Confirmed so far: the **fixed sentence at the start of the system prompt** (DSH core injects `You are an AI agent powered by DeepSeek Harness.`), and the **request-header shape** (`X-Conversation-*`, `acp-connection-id`, how `X-No-*` is used). Earlier releases of this plugin were already refused once for omitting the `X-Conversation-*` trio and once for sending `X-No-*` where the official client never does.
> - **This plugin imitates the official client at the byte level**, which is a cat-and-mouse game: every upstream change can break it until someone adapts again. **No version can promise it keeps working.**
> - **The account risk is real.** While diagnosing this, one CN account's refresh token was revoked by the upstream (`invalid_grant: User disabled`) and another was flagged 「账号存在异常行为，已被限制使用」 (`403 / 11140`). Retrying aggressively, rotating many accounts, or unusual request pacing all make that judgement more likely.
> - Upstream [corrinehu/dsh-workbuddy-connect](https://github.com/corrinehu/dsh-workbuddy-connect) **stopped maintenance on 2026-10-20**, saying it respects that boundary and will not keep adapting to these checks; the repository is scheduled to go offline on 2026-10-22. This fork is independent and still maintained, but that does not mean the road continues.
>
> **Decide for yourself whether your account is worth that risk.** If not, use the official WorkBuddy client.
---
The maintained successor of [corrinehu/dsh-workbuddy-connect](https://github.com/corrinehu/dsh-workbuddy-connect), not the upstream project. The upstream npm package is still `dsh-workbuddy-connect` (currently `0.7.8`, DSH `0.2.1-rc.2` only). This repository publishes as **`dsh-workbuddy-connect-next`**, with a different UI and account model.
Both the CN **WorkBuddy** app and the international **WorkBuddy AI** app are supported: whichever you have installed shows up as its own model group; both installed shows both, each with its own account and credit.
## How this fork differs
Compared with upstream **0.7.8** (2026-10-17). Features both trees share are not listed as ours.
| | Upstream `dsh-workbuddy-connect` 0.7.8 | This tree 0.14.0 |
|---|---|---|
| UI | two legacy plugin cards in Settings | sidebar credit card + centre dashboard + settings section page (accounts merged into one card per product; balance / used / tokens / reset sit on the line under each name) |
| Accounts | follows the desktop app's current sign-in | multi-account pool: rotation, QR, token, desktop adopt; a removed account is not swept back in; one card per product instead of one card per account |
| Credit | on the settings card only | in the sidebar, remaining or used/total, can be hidden; each account row also states used, requests, tokens and when the allowance returns |
| DSH | **`0.2.0-rc.2` only** | **`0.2.1-rc.x` only** (see “Supported DSH versions” below) |
| Update notice | bottom-right reminder | not ported |
| npm | `dsh-workbuddy-connect` | `dsh-workbuddy-connect-next` |
Both trees have: CN/AI groups, image input, reasoning-effort detection, per-account model visibility, CN enterprise credit, picker rate/promo badges, Windows Electron discovery, per-region effort-rejection codes.
**Request identity**: chat sends `WorkBuddy/
Picker groups WorkBuddy / WorkBuddy AI, with rates and free badges:
Settings page for the account pool, cycle credit and the model list:
Choose which models appear in the picker:
## Features
- **Zero configuration**: after install, pick a WorkBuddy model in chat. The plugin reuses the desktop app's sign-in and follows account switches.
- **Dashboard**: a credit card at the sidebar foot opens the centre-column panel; Settings → **DSH-WorkBuddy** manages accounts, models, context length and reasoning-level detection. The card itself can be switched off.
- **Multi-account rotation**: several accounts per product. Requests rotate across available ones; a rate-limited account is benched and retried later. Add via QR, a pasted token, or the desktop app's own sign-in.
- **Credit**: sidebar can show remaining credit or used/total; CN enterprise accounts use the enterprise billing endpoint.
- **Images**: most models accept paste or drag-and-drop.
- **Reasoning levels**: declared sets show up directly. Undeclared models can be probed from the picker on Web / Desktop (a few requests, may spend credit).
- **Visibility**: saved per signed-in account. Hiding a model only affects the picker; existing chats keep working.
## Install
Prerequisite: the WorkBuddy desktop app is installed and signed in (same for WorkBuddy AI). A mismatched DSH core fails to start.
> **⚠️ This release spans a large amount of change and has NOT been fully tested.** Display problems,
> and possibly more serious issues, may appear after upgrading. Back up `~/.dsh` before upgrading
> (especially the `.workbuddy-*.json` stores and `profiles/