dsh-opencode-go-usage-dock
English | 中文
A DeepSeek Harness web-GUI plugin that shows your OpenCode Go plan usage in a compact readout docked under the composer, aligned with the input bar's width — the same seat the shipped stats line lives in. No settings page, no sidebar entries, nothing to click through: the three usage windows (5-hour rolling / weekly / monthly) are always visible while you chat.
Features
- Composer dock readout — one compact line under the input bar, perfectly aligned with it (
conversation.composer.dock, order 10, beside the shipped stats line) - Three usage windows — 5-hour rolling / weekly / monthly, with percent used and reset time
- Health-colored dots — green < 60%, amber 60–85%, red ≥ 85%
- Hover for details — tooltip shows window name, spend limit and reset time
- Manual refresh — a small refresh button re-queries the official endpoint on demand
- Silent fallback — when opencode-go is not configured, the dock renders nothing: no error noise, no placeholder; only real failures (network / HTTP / parse) surface an error line with retry
- i18n — Chinese and English dictionaries (follows the DSH UI language)
Prerequisites
- Node.js + DeepSeek Harness with the standard
dsh webprofile (theapi-gatewayclient Remote and theconversation.composer.dockslot are part of the default composition) - An OpenCode Go subscription, with the
opencode-gomodel configured in Settings → Models - An OpenCode Go API key (
sk-opencode-…) — see [API key configuration](#api-key-configuration)
Install
Via GitHub
dsh plugin --profile web add github:xv-chang/dsh-opencode-go-usage-dockVia npm
dsh plugin --profile web add npm:dsh-opencode-go-usage-dockProfile activation
Since 0.1.2 the package declares a dsh.bundle profile patch, so dsh plugin add registers it as a profile layer automatically — no manual cordis.patch.yml editing needed.
Then restart dsh web so the host half and the served client bundle pick up the plugin.
> Installing a version before 0.1.2? Add the row manually to $DSH_HOME/profiles/web/cordis.patch.yml: > > ``yaml > - insert: > - id: opencode-go-usage-dock > name: 'dsh-opencode-go-usage-dock' > ``
Configuration
Host-side tunables live on the plugin row in cordis.yml:
- id: opencode-go-usage-dock
name: dsh-opencode-go-usage-dock
config:
baseUrl: https://opencode.ai/zen/go/v1/usage # default
timeoutMs: 15000 # default| Key | Default | Meaning |
|---|---|---|
baseUrl | https://opencode.ai/zen/go/v1/usage | The usage endpoint. |
timeoutMs | 15000 | Fetch timeout in milliseconds. |
API key configuration
The plugin resolves the key from the DSH credentials seam only:
OPENCODE_GO_API_KEYin$DSH_HOME/.credentials.yaml(or as an environment variable).
No OpenCode CLI files are consulted — this plugin is a DSH feature and does not depend on an opencode installation.
Behavior
| State | Dock renders |
|---|---|
| opencode-go not in Settings → Models | nothing (silent) |
| No API key found | nothing (silent) |
| Request failed (network / HTTP / parse) | red error line + retry button |
| Success | OpenCode Go ● 滚动 1% ● 本周 20% ● 本月 11% [刷新] |
How it works
A dual-face plugin. The Host publishes the opencodeUsage Typert Remote service; the Client mounts it, registers the conversation.composer.dock slot, and renders the readout. Communication rides the harness /api RPC carrier.
| File | Role |
|---|---|
index.js | Host half — OpencodeUsageGateway (TypertRemoteService, service key opencodeUsage) |
typert.host.js | Hand-written Typert host manifest, registered via exports["./typert"] |
client.js | Browser bundle in window.__ModuleLoader__.load format — mounts the Remote, registers the dock slot, renders the readout |
package.json | Dual-face declaration: main + exports["./client"] + exports["./typert"] + dsh.client + dsh.bundle |
The usage endpoint
GET https://opencode.ai/zen/go/v1/usage
Authorization: Bearer <API_KEY>Returns (community-verified shape; not yet in OpenCode's public docs, so parsing is defensive):
{
"usage": {
"rolling": { "status": "ok", "percent": 9, "resetsAt": "2026-08-14T07:20:04.810Z" },
"weekly": { "status": "ok", "percent": 12, "resetsAt": "2026-08-17T00:00:00.810Z" },
"monthly": { "status": "ok", "percent": 6, "resetsAt": "2026-09-09T00:41:03.810Z" }
}
}percent is 0–100; resetsAt is ISO-8601.
FAQ
pnpm reports "missing peer react / @deepseek-ai/..." during install — is that normal? Yes, safe to ignore. Those dependencies are provided by the DSH runtime: DSH resolves bundles two-anchor (installation first, profile second) and maintains a flat fallback directory at $DSH_HOME/profiles/node_modules so the plugin resolves the installation's built-in @deepseek-ai/* and react through ordinary Node parent-walk. pnpm only warns because the peers are not part of the profile dependency tree at install time; loading is unaffected. If you also see declares no dsh.bundle, upgrade to 0.1.2+ (it then registers itself as a profile layer automatically).
The dock does not appear. The slot is session-scoped: open any conversation. Then check, in order: (1) opencode-go is present in Settings → Models; (2) an API key resolves (see above); (3) the plugin row is in the profile patch layer and dsh web was restarted.
I see "API Key 无效或已过期 (401)". Your key is wrong or expired — re-issue it in the OpenCode dashboard and update the credentials seam.
Quota limits shown in tooltips ($12/$30/$60) drift. They follow the OpenCode Go plan and are displayed for context only; the endpoint response does not include them.
License
MIT