dsh-balance-stats

DeepSeek users who run long tasks keep hitting the same wall: the balance still looks fine, but where exactly the money went, how much was spent today, and how many days the current pace will last are all buried between an aggregate bill and scattered local logs. dsh-balance-stats pulls all of that into one panel. A floating capsule in the top-right corner ticks a live balance and estimated runway every three seconds; the Settings page opens with four KPI cards for balance, daily and monthly spend, and a status lamp that turns red when funds are low. Behind the numbers, every request is itemised by its exact peak or off-peak timestamp, cache bucket, and model.

It goes further than a ledger. Set a daily budget and a progress bar turns yellow at eighty percent and red past the cap, a quick glance before launching a batch job saves more trouble than staring at the balance. Cache-hit ratio below fifty percent triggers a per-workspace warning, since a miss costs twenty to sixty times a hit, making it the single biggest lever for cutting spend. The ten most expensive requests, a per-workspace cost ranking, and a peak-to-off-peak savings estimate are all pre-computed. And when the total is a few cents off the official bill, the plugin lists the exact call counts of title generation and web-search requests that local logs cannot price, so the gap is explained rather than hand-waved.

It is built for anyone who treats DeepSeek API spend as a line item to manage: developers running bulk inference, teams juggling multiple workspaces, or anyone who would rather see the number turn yellow today than discover the balance gone at month-end. All data is read from local session logs and the official balance API; the API key never leaves the host process. Released under the MIT licence.