DeepSeek Harness Plugin: dsh-opencode-usage
dsh-opencode-usage is a zero-configuration plugin for the DeepSeek Harness Web Composer, designed to address the issue of users being unaware that their OpenCode Go quota has been exhausted. The plugin displays the remaining quota percentage in a compact stats line below the input box, supporting rolling, weekly, and monthly views. It uses a Host/Client separation architecture to automatically read configuration and securely fetch data without requiring a build. After installation, users can click the battery icon to view details, effectively helping them monitor costs.
Read Moredsh-opencode-usage: View OpenCode Zen Balance and Go Usage Window in the DSH Interface
`dsh-opencode-usage` is a Web GUI plugin for DeepSeek Harness (DSH), designed to help developers intuitively view OpenCode Zen balances and Go usage windows. The plugin provides donut chart visualization, usage detail panels, and intelligent Cookie normalization configuration, with built-in anti-abuse mechanisms. It supports managing cookies, cache duration, and timeout settings via environment variables or configuration files, and offers a JSON API for external calls to refresh or configure data, ensuring security and permission control.
Read Moredsh-opencode-usage: Displaying OpenCode Go Package Usage in the DSH Web GUI
dsh-opencode-usage is an open-source plugin (MIT licensed) developed for the DSH web GUI, designed to monitor OpenCode Go package usage in real time. The plugin provides a persistent badge below the composer input box, displaying usage percentages and reset countdowns across three windows—rolling, weekly, and monthly—with support for automatic refresh. Clicking the badge expands a detailed card showing progress bars, real-time countdowns, and configuration options for API Key, Base URL, and refresh interval. Additionally, it offers a parameterless tool `opencode_go_usage` that allows agents to directly query package balance during conversations. The plugin is developed purely from source code with no build steps, handles requests through same-origin routing to ensure API Keys do not enter the browser, and defaults to reading from environment variables.
Read More