DeepSeek Harness Plugin Hub

发布与管理完整 Harness Profiles,发现适合你的插件。

探索

插件目录环境预设文档中心动态

社区

发布插件联系我们报告问题

相关链接

Plugin Hub GitHubDeepSeek Harness 官方项目系统状态隐私说明
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

独立、非官方社区项目,与 DeepSeek 官方无隶属、授权或背书关系。

Subscription Logins — DeepSeek Harness 插件(DSH Plugin)
DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录
← Plugins
S

dsh-subscription-logins

Subscription Logins

在 DSH 网页端管理 OpenAI、Anthropic 和 Z.AI 订阅凭据

插件会安装到这里;不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add github:n0pe-sled/subscription-logins#9196d410b405028c8fe298147b097d3222fba631
README兼容性版本

兼容性与来源证明

Subscription Logins 以 dsh-subscription-logins 发布,当前版本为 0.1.0。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

DSH 兼容范围
*
运行环境
web
发布来源
github
Registry 更新时间
2026/9/14

版本

0.1.0stable
2026/9/14

相关插件

正在加载相关插件…

最新版
0.1.0
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
未提供
文件数
未提供
Surface
web
许可证
未声明
发布源
github
GitHub
★ 0
周下载
0
最近提交
2026/9/13
查看源码 ↗
README Badge

点击下方 Badge 复制 Markdown,粘贴到 README 即可。

这是你的 Plugin?认领权益 · 优先安全扫描

验证 package.json 声明的 GitHub 仓库,即可管理这个公开页面。认领后,Hub 会优先安排当前版本的安全扫描,并在通过后公开展示结果。

认领这个 Plugin →
报告问题

相关插件

继续浏览 security-access 分类下经过校验的插件。

Doctor@linxin666/dsh-doctorDSH 配置档案的事务性救援模式,配备受监督的启动器、隔离的恢复容器、确定性修复、健康监控以及本地 Web 恢复控制台Pocketdsh-pocket把 DeepSeek Harness 装进你的口袋:一个包、一个设置页,手机扫码即同步访问电脑上的 DSH(局域网 + 公网,实时同屏)。DSCODE@toddzheng024/dscode-bundle完整的 DeepSeek 编码代理,支持持久化 shell、Ultra 协作和自动权限审查。Auto Reviewdsh-auto-review针对 DeepSeek Harness 审批请求的第二模型 AI 自动审查:只读审查子代理在审批应答链上决定允许或拒绝,并采用故障关闭回退机制和完整的会话日志审计。

README

dsh-subscription-logins

Manage subscription credentials for DSH's openai-codex, anthropic, and zai providers. The plugin adds a short Logins entry beside Models in Settings and drives the provider flows supplied by pi-ai.

This is a pure bundle plugin. It does not patch DeepSeek Harness. Its composition layer mounts the published @deepseek-ai/dsh-authorization service, which causes the existing llm-pi-ai plugin to register its provider login flows. The plugin's host half exposes only the openai-codex, anthropic, and zai flows to its own browser half through a Typert Remote.

Install

dsh plugin --profile web add /path/to/deepseek-harness-plugins/subscription-logins

Restart dsh web, then open Settings → Logins. Name each login as you add it, for example Work or Personal. The page keeps multiple credentials per provider and marks one active. Select Use to change the account used by the next model request.

  • For ChatGPT, select Sign in with ChatGPT, open the verification page, and enter the displayed code if OpenAI uses the device-code path.
  • For Claude, select Sign in with Claude, finish the browser flow, and paste the callback URL or authorization code if requested.
  • For Z.AI, create an API key after subscribing to the GLM Coding Plan, then enter it in the masked prompt. Z.AI uses API keys rather than browser OAuth.

The zai route uses pi-ai's dedicated Coding Plan endpoint, https://api.z.ai/api/coding/paas/v4. Z.AI says Coding Plan benefits are limited to supported tools and products. Confirm that DSH usage complies with the current GLM Coding Plan usage policy before relying on subscription quota. See Z.AI's Coding Plan quick start for API key setup.

The Claude option exposes pi-ai's existing Anthropic OAuth flow, but it does not promise that requests will be included in a Claude Pro or Max subscription. Anthropic's published login policy says third-party tools should normally use API keys. It may restrict OAuth access or charge usage credits. See Anthropic's account login policy.

OpenAI currently labels device-code authentication as beta. If it is unavailable, enable device-code login in your personal ChatGPT security settings or ask your workspace admin to allow it. A normal browser callback flow may be offered instead.

After login, the plugin adds the matching openai-codex, anthropic, or zai provider to Settings → Models with an empty native profile. Existing provider settings are never replaced. Choose one of that provider's models for a session.

The adapter still reads its canonical llm-pi-ai/<provider> record. The plugin archives named credentials under its own credential scope and copies the selected credential into that canonical record. Before switching, it saves the current canonical record back to the active archive so token refreshes survive account changes. An existing canonical credential is imported as Existing login and can be renamed.

Removing a saved login deletes its archived credential. Removing the active login also deletes the provider's canonical record. These records contain sensitive access tokens, refresh tokens, and API keys. Protect the DSH home directory, and never commit or share its credential files.

Why this is a separate Settings page

The public client extension API has a settings.section slot, but the built-in Models page does not declare a slot inside provider cards. Registering a neighboring page uses the supported plugin API and survives client rebuilds. Modifying ProviderEditor or the host API proxy would put part of the feature back into harness core.

Development

pnpm install
pnpm typecheck
pnpm build
pnpm test

The built node and browser files under lib/ are committed so local and tarball installs do not need a build step.