AI Agent Hub
Back to plugins
🧰

dsh-provider-usage

Web Tools Updated 2026.09.15

Run the following command in DeepSeek Harness:

dsh plugin install loommii/dsh-provider-usage

Paste the following prompt into your AI chat to install this plugin:

In the DeepSeek Harness terminal, run dsh plugin install loommii/dsh-provider-usage to install this plugin. Source repository: https://github.com/loommii/dsh-provider-usage .

About this plugin

Juggling several AI subscriptions means constant tab-switching just to check balances and quota windows—OpenCode Go's 5-hour/weekly/monthly caps, a DeepSeek account balance, a custom Command Code monthly limit. dsh-provider-usage collapses all of that into a single persistent card anchored to the bottom-right of the DSH web interface. It auto-refreshes every 30 seconds, surfacing usage percentages, progress bars, and reset countdowns at a glance, so you never have to leave your workspace to answer the question "how much do I have left." The card is freely draggable, can dock to a screen edge as a slim handle, and supports multiple provider instances with one-click switching.

Beyond live quotas, the plugin ships a fully offline local token dashboard. It reads session files under $DSH_HOME/sessions and aggregates same-day token consumption by provider and model—no network call required. API keys are resolved in-process, masked on screen, and stored with AES-256 encryption locally; nothing leaves your machine.

If you run two or three AI subscriptions inside DSH and are tired of refreshing browser tabs every few minutes, this plugin turns usage tracking into a glanceable, always-present widget. Configure each provider once, and the card stays quietly in the corner, updating itself so you always know where you stand.

Use Cases

  • Juggling multiple AI subscriptions and needing quota and balance at a glance
  • Avoiding browser tab-switching by keeping usage info inside the DSH workspace
  • Tracking same-day token consumption offline, broken down by provider and model

Best For

  • Developers running two or more AI subscriptions inside DSH
  • Users who prefer offline local token tracking without network calls
  • Users monitoring quotas across OpenCode Go, DeepSeek, and other platforms