@cs-qyzhang/dsh-llm-quota
Shows the active model provider's remaining balance or coding-plan quota in DeepSeek Harness (dsh).
安裝
npx -p @deepseek-ai/dsh dsh plugin --profile web add @cs-qyzhang/dsh-llm-quota@latest說明文件
閱讀完整 README ↗使用与配置 / Usage and Configuration
插件会根据当前模型的 provider 自动查询额度。完整的 provider ID、支持范围和凭证要求见供应商文档与 DSH provider 清单。
The plugin automatically queries quota based on the current model's provider. For complete provider IDs, supported scope, and credential requirements, see the provider documentation and DSH provider list.
-
凭证:默认复用 dsh 中已有的推理凭证。需要额外控制台凭证的供应商,可在 Plugins → Installed plugins → 模型额度 → 供应商额外凭证 中配置;各供应商的具体要求见供应商文档。
-
高级配置:在 Plugins → Installed plugins → 模型额度 的「插件配置」中可调整
queryIntervalSeconds、history、historyDefaultRange,并用 JSON 编辑providers与providerModules。保存会重建 Host 的路由、缓存与采集器;新增或修改自定义 Provider 的展示、文案或凭证字段后,需刷新已打开的页面以重新获取 manifest。historyDefaultRange默认近 1 小时,可选近 1 / 4 / 12 / 24 小时、7 天或 30 天,重新打开详情生效。自定义模块与手工 YAML 示例见接入新的额度体系。 -
历史数据:按查询间隔采集(默认 30 秒),仅在 Provider 声明的额度指标变化时写入本地 SQLite。关闭
history会同时停止采集、写入并移除历史查询路由。存储路径、保留策略、抽样和趋势图说明见架构文档。 -
Credentials: Reuses inference credentials already configured in dsh by default. For providers that require additional console credentials, configure them in the plugin's additional provider credentials section. See the provider documentation for provider-specific requirements.
-
Advanced configuration: Under Plugins → Installed plugins → Model quota, Plugin settings exposes
queryIntervalSeconds,history,historyDefaultRange, and JSON editors forprovidersandproviderModules. Saving rebuilds the Host routes, cache, and collector; refresh an already-open page after changing a custom Provider's view, messages, or credential declarations so the Client fetches the new manifest.historyDefaultRangedefaults to the last 1 hour, with options for the last 1 / 4 / 12 / 24 hours, 7 days, or 30 days; reopen the details to apply it. See adding a quota system for custom modules and manual YAML examples. -
Historical data: Collects on the query interval (30 seconds by default) and writes to local SQLite only when a Provider-declared quota metric changes. Disabling
historystops collection and persistence and removes the history query route. See the architecture documentation for the storage path, retention policy, sampling, and trend charts.