dsh-llm-opencode-go

See the usage

Usage has three entries, all reading the same facts:

Entry	Where
The quota capsule at the sidebar's foot	Beside Settings. One row, three groups — ◉ 5H 92% │ ◉ 周 58% │ ◉ 月 9% — visible without a click; that row opens the usage panel, and the gear beside it opens the plugin's configuration page.
The usage panel	From that row, or the keyboard (desktop Ctrl/Cmd+U): the subscription's three windows first, this route's counters under them, and a header that stays on screen as they scroll — the way to the plugin's configuration page, and an × back to the conversation.
Settings → Built-in plugins	A tab carrying the same content as the panel.

All three need the web client; a deployment without one has none of them and is otherwise unchanged. See Configuration.

Configuration

The config block above is all that is required; every other key is optional. The full field table, catalog shaping, and image input live in Configuration.

Point it at another credential reference, if you would rather the plugin read a differently-named variable:

config:
  apiKeyEnv: OC_KEY

The value is never read from the config file itself, only the variable name.

Or configure it from the web client. Settings carries an OpenCode Go settings row of its own, beside the pages the shell ships, and the same page is behind the sidebar's Plugins page: the dsh-llm-opencode-go bundle's opencode-go row has a Configure control. Either door opens the plugin's own page: the API key, the credential reference it is stored under, one switch per catalog model for what the picker offers, the model variants, a control that re-reads the service's model list, and what this route has spent. The key is written to the credential store, never to cordis.patch.yml, and the page is mounted only by a deployment that serves the web client. See Configuration.