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.
Install
via npm
Resolves a published tarball rather than cloning the repository, and installs without any extra setup. Swap `web` for your profile name if you run another one.
via GitHub · npm package
Installing from GitHub runs the project's build script, which pnpm blocks until you allowlist it — run the command once and pnpm prints the exact key to add under `allowBuilds` in ~/.dsh/profiles/web/pnpm-workspace.yaml.
What happened when we ran it
Installed cleanly when we ran it
Every command here is run in a throwaway container against a clean profile, and the result is whatever the harness recorded — not a guess from the source. Last run 14d ago.
Show it in your README
For maintainers: the badge serves this listing's latest sandbox verdict, so a re-run updates it on its own — and it links readers to the full result here.
Due diligence
What it is — dsh-usage-stats provides multi-provider account monitoring and token usage analytics for the DeepSeek Harness web GUI.
Who it is for — When using DeepSeek Harness web profile for multi-provider token usage analysis and account balance monitoring, it is suitable to install. If a user only needs to analyze token usage for a single provider without cross-provider data aggregation, they can monitor using other methods.
Watch out — Requires providing API key or token to fetch account data. Sandbox testing passed: installed in a fresh profile and registered by Harness. Will execute shell commands.
The verdict — If multi-provider token usage and balance analysis is needed, I would install it because it offers fee estimation and budget alerts, but the premise is that credentials are provided.
Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.
dsh-usage-stats is a DeepSeek Harness plugin that monitors configured provider accounts and analyses token usage in the DeepSeek Harness web interface. DeepSeek Harness loads it in the web profile, where it adds a Usage/Balance entry and serves five loopback-only GET endpoints. The plugin reads provider profiles and credentials resolved by DeepSeek Harness from ~/.dsh/.credentials.yaml, then sends the required credentials to validated provider URLs for balance or subscription checks. It aggregates local token data by day, provider and model, while keeping keys, cookies, management PATs and upstream responses on the server.
The dashboard covers balance providers, token-plan quotas, monthly calendar drill-downs, cache-hit rates, account status thresholds and adapters including New API, Sub2API, OpenRouter, OpenCode Go, Z.ai, Kimi and MiniMax. Background refresh starts with the service and repeats every five minutes; manual refresh forces the selected account only. DeepSeek Harness plugin configuration can add monitors under the existing dsh-usage-stats entry, including restricted declarative GET queries using JSON Pointer extraction.
This is for developers who need one local view across several provider accounts and usage sources. It is a poor choice where remote account checks are unavailable or credentials must never leave the local service process: unsupported providers still yield token statistics, but no balance is inferred. The plugin also requires the DeepSeek Harness web profile and a compatible @deepseek-ai/dsh version. Its terminal surface is the Node-based installation and update path; its runtime credential and network surface exists to query configured provider endpoints.
DeepSeek Harness reads credentials from ~/.dsh/.credentials.yaml; the installer does not read, create or modify this file. Provider profiles normally supply apiKeyEnv. Account-specific references include OPENROUTER_MANAGEMENT_KEY, OPENCODE_GO_API_KEY, ZAI_API_KEY, KIMI_API_KEY and MINIMAX_API_KEY. Optional region keys are ZAI_API_REGION (global by default) and MINIMAX_API_REGION (global by default). OpenRouter requires a management key, not a normal inference key.
Custom monitors are merged into the existing Cordis entry named dsh-usage-stats:
| Key | Purpose |
|---|---|
monitors.<provider>.adapter |
Selects an adapter such as new-api, sub2api, general or declarative |
warning.warnBelow / criticalBelow |
Absolute balance thresholds |
request.path |
Restricted GET path for a declarative monitor |
extract.* |
JSON Pointer locations for extracted values |
Declarative monitors use credentialRef and do not execute JavaScript. Unknown provider IDs, adapters or invalid mappings stop startup before routes and timers register.
DeepSeek Harness manages the plugin with dsh plugin --profile web update dsh-usage-stats and dsh plugin --profile web remove dsh-usage-stats. After adding or updating the plugin, restart the running dsh web process and hard-refresh the browser. The alternative npx installer supports --dry-run, --check and --no-enable, but it is a separate installation path and must not be combined with a manual Cordis entry.
DeepSeek Harness requires the web profile and @deepseek-ai/dsh >= 0.1.0-rc.6. The service refreshes configured accounts and local token aggregates at startup and every five minutes, regardless of whether the panel is open. The browser requests only the selected provider. A manual refresh updates tokens and the provider list, and forces the selected account rather than all accounts.
Providers without a public account interface can still contribute token usage, but their account card reports that balance checks are unsupported. OpenCode Go uses a non-public bearer usage endpoint that may change. Cookie credentials are equivalent to login credentials. Future timestamps are excluded, and “last 14 days” uses local calendar dates.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub
Same category
bowenliang123
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.
Installed cleanly when we ran it
Han-1413141
Per-session and daily API cost, budget with usage %, official balance, history dashboard, and one-click official price sync with peak/off-peak pricing.
Installed cleanly when we ran it
wssfk12138
Tracks DeepSeek token usage, per-call and session costs, and account balance with cache-aware charge animations in the DSH Web UI.
Installed cleanly when we ran it
zh667
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.
Installed cleanly when we ran it
PolinniZhong
Personal center for DeepSeek Harness: cross-session usage statistics, per-model cost estimation, global custom instructions, a global font-size adjuster, a data-driven desktop pet with bitmap & vector skins, and a conversation status overview, all local and offline.
Installed cleanly when we ran it
Aisland-SJL
🌊 Persistent dock & fully-customizable balance/usage panel for DeepSeek Harness — activity heatmap, dual-channel comparison, local-only & privacy-first
Installed cleanly when we ran it
