DeepSeek Harness Plugin Hub

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

探索

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

社区

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

相关链接

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

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

Key Manager — DeepSeek Harness 插件（DSH Plugin）
DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录
← Plugins
K

@rycbartbad/dsh-key-manager

Key Manager

为 DeepSeek Harness 的每个提供商配置多个 API 密钥：维护带备注的密钥池，直接从“设置 → API 密钥”切换当前密钥，并确保每次切换都会在下一次模型调用时生效。

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

npx -y @deepseek-ai/dsh plugin --profile web add github:Rycbartbad/dsh-key-manager#96ac719215f28ee4a85053586da41df168b84caf
README兼容性版本

兼容性与来源证明

Key Manager 以 @rycbartbad/dsh-key-manager 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。

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

版本

0.1.0stable
2026/8/29

相关插件

正在加载相关插件…

最新版
0.1.0
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
未提供
文件数
未提供
Surface
web
许可证
MIT
发布源
github
GitHub
★ 0
周下载
0
最近提交
2026/8/30
查看源码 ↗
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-key-manager

Multiple API keys per provider for DeepSeek Harness.

Keep a pool of API keys for each provider configured in Settings → 模型 (Models), annotate each key with a note, and switch the active key from Settings → API 密钥 — every switch really takes effect on the next model call.

Features

  • Per-provider key pools — for every configurable provider exposed by the Models page (only providers that actually have a key reference are listed).
  • Notes — annotate each key (e.g. "personal", "team", "billing A"); the currently-in-use key can be renamed too.
  • Switch that really applies — activating a key writes it through the harness credential seam. When the native reference is shadowed by the process environment or a .env file, the plugin takes over by storing the value under a plugin-managed reference and repointing the provider's apiKeyEnv at it — the Models page shows which reference is in effect.
  • Current-use pinned first — the key actually in use always sits on top with a green badge; keys missing the pool show as a "live" row.
  • Defaults to the provider in use — the page pre-selects the provider behind the currently-selected model.
  • Durable, no hardcoded paths — the registry file lives next to the harness data directory (derived at runtime from the settings document path).

Storage note: key values are persisted in plain text in the harness data directory (~/.dsh/dsh-key-manager.json), the same level of protection the harness itself applies to .credentials.yaml. Lock down the directory if you share the machine.

Install

dsh plugin --profile web add dsh-key-manager

Restart dsh web, then open Settings → API 密钥.

How it works

PieceWhere
Settings section api-key-managerlib/client.js (web module)
Same-origin JSON API /plugins/dsh-key-manager/*lib/index.js
Key pool registry~/.dsh/dsh-key-manager.json (derived at runtime)
Active key writeharness credentials service (native ref, or plugin-managed takeover ref)
Provider apiKeyEnv repointharness settings service (llm-* namespace)

License

MIT