dsh-opencode-go

Developers juggling two OpenCode GO accounts and one CommandCode account know the drill: quotas are scattered across three separate dashboards and three different billing windows—rolling 5-hour, weekly, monthly—and it is easy to unknowingly hit a ceiling mid-session. dsh-opencode-go condenses that oversight into a single persistent chip in the DeepSeek Harness Web conversation header, showing all accounts’ three quota windows at a glance with color-coded weekly percentages (green, orange at 70%, red at 90% or restricted) and a per-account breakdown with rolling-window countdown on hover.

The chip auto-refreshes every three minutes and also provides a manual refresh button. Usage data is cached at the module level, so switching conversations or re-mounting the component never triggers a redundant upstream call. If one account credential fails or its endpoint times out, only that row displays an error while the others keep updating normally. All API keys stay on the host side in .credentials.yaml or environment variables; the browser never sees plaintext secrets.

Built for developers who run multiple OpenCode GO slots alongside a CommandCode subscription within DeepSeek Harness Web and want an always-on answer to the question: how much quota is still left?