AI Agent Hub
Back to plugins
🖥️

dsh-ocgo-quota

Client Updated 2026.08.26

Run the following command in DeepSeek Harness:

dsh plugin install fuzz1og/dsh-ocgo-quota

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

Run dsh plugin install fuzz1og/dsh-ocgo-quota in the DeepSeek Harness terminal to install this plugin (source: https://github.com/fuzz1og/dsh-ocgo-quota); restart DSH after installation.

About this plugin

Anyone who grinds through long OpenCode Go sessions in DSH has felt the flow snap: you hit an uncertain point about remaining quota, switch tabs, open a browser, hunt for the usage page, and wait. dsh-ocgo-quota removes that step entirely. A small, unobtrusive widget appears in the bottom-right corner of the DSH UI, showing your rolling 5-hour, weekly, and monthly quota at a glance—no tab-switching, no context loss.

The data is pulled directly from the official OpenCode Go usage endpoint. Under the hood the plugin caches responses for 45 seconds and coalesces concurrent polls into a single in-flight fetch, so even if multiple components query at the same moment the server sees only one request. Credentials are resolved through DSH's credentials seam: it looks for OPENCODE_GO_API_KEY in the environment first, then falls back to the same key in your local .credentials.yaml. There are zero runtime dependencies—only Node built-ins and the webServer service—so there is nothing to update and nothing to break after a DSH restart.

This plugin is for developers who use OpenCode Go daily inside DSH and want quota awareness without friction. The widget sits quietly in your peripheral vision: one quick look when you need it, completely invisible when you do not.

Use Cases

  • Glance at remaining OpenCode Go quota without leaving the DSH editor
  • Multiple components poll usage simultaneously with automatic request coalescing
  • Track rolling 5-hour, weekly, and monthly quota changes in real time without a browser tab

Best For

  • Developers who use OpenCode Go daily within the DSH environment
  • Engineers who want to minimize context switching and protect deep work
  • Technical users who need constant visibility into API quota consumption