lizhouai/dsh-provider-usage

A draggable floating ball over the DeepSeek Harness Web GUI and Desktop app that shows every configured provider's balance, quota window and spend in one panel.

Each adapter maps one route kind to its real endpoint, covering DeepSeek balance, DeepSeek Account wallet, Moonshot, Kimi Coding, OpenRouter credits, GitHub Copilot, OpenAI Codex subscription windows, OpenAI and Anthropic organisation spend (admin keys required), MiniMax Coding Plan, Z.ai GLM Coding Plan, OpenCode, Vercel AI Gateway, xAI prepaid balance and the two Volcengine Ark plans; routes with no public balance API are listed as unsupported instead of being dropped. Credentials are resolved per request through the harness credentials service and never cached or written to disk, and OAuth grants are refreshed transparently. The floating ball is draggable and its position persists, the panel resizes by dragging its top edge, and the halo encodes the health of the provider the focused session is actually using, so switching sessions re-highlights without re-selecting a model. Refresh interval, balance thresholds and the bilingual UI toggle all persist in localStorage.

Usage & Billing ★ 4
View on GitHub ↗

Install

dsh plugin --profile web add dsh-provider-usage@latest

Copied verbatim from the README's Web GUI install block. package dsh-provider-usage, registry latest 0.3.16, and its repository field resolves back to github.com/lizhouai/dsh-provider-usage. The desktop app owns its own profile (~/.dsh/profiles/desktop), so it needs the same install with --profile desktop; there is no separate desktop build. Restart dsh web and refresh the page, and check the version badge in the panel header, because a profile's minimumReleaseAge cooldown can silently keep an older version (pinning an exact version makes dsh exempt it).

Compatibility

Zero configuration for well-known routes: the plugin enumerates the provider routes registered in the current profile through ctx.llm and applies a per-kind wire adapter. The DeepSeek account card depends on the harness route composed in dsh >= 0.1.7 and reads the built-in DeepSeek Account sign-in, so it stays hidden until a sign-in is stored. Two families need extra setup: OpenAI Codex authenticates through an OAuth grant rather than an API key, and the Volcengine Ark Agent/Coding Plan routes need an IAM AK/SK pair for a signed control-plane call, both documented in the repo's setup guides.

Details

Alternatives

vinyumao/dsh-opencode-usage · kelearns/dsh-token-usage · Hjay1101/dsh-opencode-go-usage

More plugins in Usage & Billing

Browse more in Usage & Billing

Guides for Usage & Billing plugins