AI Agent Hub
Back to plugins
🧰

dsh-opencode-go-usage

Web Tools Updated 2026.09.05

Run the following command in DeepSeek Harness:

dsh plugin install mouseteamlucky/dsh-opencode-go-usage

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

Run dsh plugin install mouseteamlucky/dsh-opencode-go-usage in DeepSeek Harness to install this plugin; the source code is available at https://github.com/mouseteamlucky/dsh-opencode-go-usage

About this plugin

Juggling multiple OpenCode Go API keys means hopping between rolling, weekly, and monthly quota windows scattered across different dashboards. dsh-opencode-go-usage collapses all of that into a compact floating widget pinned to the right edge of the DSH web page, giving you a persistent at-a-glance overview without ever leaving the browser.

Expanding the panel reveals one card per key (the active key is marked with a star), each showing three progress bars for rolling, weekly, and monthly usage, precise percentages, and reset countdowns. Rate-limited windows are flagged with a warning icon, and per-key errors appear inline. The collapsed badge itself pulses in green, orange, or red to reflect the most urgent window so you can sense risk at a glance. The key pool is auto-discovered from .credentials.yaml with a graceful fallback to the environment-level key; the panel polls and auto-refreshes, with a manual refresh button as backup; and the entire UI adapts to DSH light and dark themes as well as bilingual displays.

This plugin is built for DSH users running multiple OpenCode Go keys, teams managing a shared key pool, or anyone who simply wants quota awareness without flipping through tabs every few minutes.

Use Cases

  • Monitor quota consumption across multiple active keys at a glance
  • Catch rate-limit windows before they trigger via reset countdowns
  • Track shared key pool status without switching browser tabs

Best For

  • Developers managing multiple OpenCode Go API keys concurrently
  • DSH teams maintaining a shared key pool
  • Anyone who needs quota visibility without repeatedly checking dashboards