masknull/dsh-workbuddy-connect

DSH WorkBuddy Connect

将 WorkBuddy(国内版 / 国际版)的模型接入 DeepSeek Harness —— 插件自带浏览器登录,无需 WorkBuddy 桌面 App。WorkBuddy CN & international models for DeepSeek Harness; the plugin signs itself in. 支持 DSH 0.1.5-rc.1+。

待分类codebuddydeepseekdeepseek-harness

DSH WorkBuddy Connect

## ⚠️ 本仓库已归档(Archived)
归档原因:藤子加强风控检测,开发者多个账号已被上游风控处置。 WorkBuddy CN 的全部 chat 请求现在返回:
```json
{"code":11140,"msg":"request illegal","requestId":"","displayMsg":{"en":"Your account has been restricted due to unusual activity","zh":"账号存在异常行为,已被限制使用","zh-Hant":"帳號存在異常行為,已被限制使用"},"displayTips":{"en":"We detected unusual activity on this account. Submit feedback to appeal this restriction","zh":"系统检测到该账号存在异常使用行为,如需申诉请提交反馈","zh-Hant":"系統偵測到此帳號存在異常使用行為,如需申訴請提交回饋"},"actions":["EDIT_INPUT","SUBMIT_FEEDBACK"]}
`
同一台机器上,官方 WorkBuddy 桌面客户端得到的是同样的响应,因此这不是插件请求形态的问题,而是账号层面的限制。藤子已经显著加强了客户端身份与渠道校验,继续维护 2dsh 已经没有意义。当然国际版目前可以正常使用。
感谢一路以来的使用与反馈。我们下个 2dsh 项目见。
## ⚠️ This repository is archived
Reason: Tencent tightened risk control, and multiple developer accounts have been restricted upstream. Every WorkBuddy CN chat request now returns the response above (code 11140, "Your account has been restricted due to unusual activity").
The official WorkBuddy desktop client receives the same response from the same machine, so this is not the plugin's request shape — it is an account-level restriction. With client identity and channel verification tightened this far, keeping the 2dsh integration alive no longer makes sense. The international build still works.
Thanks for everything. See you in the next 2dsh project.