dsh-key-manager
Manage multiple API keys per provider in Settings → API 密钥: keep a pool of keys with notes, switch the active key with one click, and the switch really takes effect on the next model call.
在设置 → API 密钥中为每个提供商管理多个 API 密钥：密钥池加备注、一键切换当前使用密钥，切换后下一次模型调用立即生效。
How to install
dsh plugin add github:Rycbartbad/dsh-key-manager About
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…
Recommendation signals
Meta
- License
- MIT
- Language
- JavaScript
- GitHub stars
- 0
- mo. downloads
- –
- Last push
- 2026-08-30
- Created
- 2026-08-29
Links
Basic safety check
- Findings
- curated 收录但无 npm 包/安装命令
- Sources
- curated:awesome-dsh-plugin.com, curated:awesome-dsh-plugin/awesome-dsh-plugin
- Topics
- api-key, deepseek-harness, dsh-plugin
Related plugins
dsh-context
bowenliang123/dsh-context
DSH context insight panel: Context dashboard + /context command + Context browser — one-stop context lifecycle management with categorized composition, content details, evolution trends, compaction/injection events, and stats.
dsh-cost-meter
Han-1413141/dsh-cost-meter
Per-session and daily API cost, budget with usage %, official balance, history dashboard, and one-click official price sync with peak/off-peak pricing.
dsh-usage-stats
Ychris12138/dsh-usage-stats
Multi-provider usage dashboard with provider/model token breakdowns, calendar drill-downs, account balances, and OpenCode Go / Z.ai subscription quota tracking.
TokenLedger
zh667/TokenLedger
Sidebar usage panel that attributes tokens to the relay site that served each request, read from your existing provider config: today/month/all-time totals, per-site and per-model breakdowns, a year activity heatmap, and New API / Sub2API / DeepSeek balances.