dsh-commandcode-usage

The most annoying part of running heavy Command Code workloads is rarely model quality—it is the invisible quota ceiling. The five-hour window is about to fill up, the weekly reset time slips out of memory, and the monthly Credits balance lives in a browser tab you have to hunt down. dsh-commandcode-usage brings all of that inside the DSH interface: a Host-side poller calls the same-origin /alpha/* endpoints (whoami, usage, billing, subscriptions) at a configurable interval, normalises the results into a single in-memory store, and exposes them through same-origin JSON routes that the browser can read without ever touching the API key.

Beyond a top-level dashboard, the plugin tracks per-turn consumption. A SessionWatcher listens for genuine usage fields inside assistant messages, settles the cost at turn end, and publishes the token count to turn-cost.json with an incrementing sequence number so the front-end can poll for changes cheaply. In multi-account setups each slot resolves, polls, and degrades independently; the credential chain walks through config literals, the DSH credentials service, a launch-time environment variable, and the official CLI auth file in order, while the browser side only ever sees aggregated JSON.

If you run long conversations or batch jobs through DSH on Command Code, or your team shares the platform across several accounts and everyone needs to watch their own quota, this plugin turns constant tab-switching into a single glance at the sidebar usage bars.