@easytz/dsh-ui-balance

LIMITATIONS

Known limitations

- Only DeepSeek and Moonshot/Kimi expose a public balance endpoint; other vendors need one before support can be added. - DeepSeek official model prices are auto-synced from the official pricing page (once at startup, then every 12 hours). On failure the last real table keeps being used and the panel says so; the bundled defaults only apply if a sync has *never* succeeded. Other vendors' prices still come from local configuration — worth checking now and then. - The price timeline only starts when this plugin is installed. Calls older than its first entry are priced with the oldest table on hand — nobody recorded what the price was before that. - Costs are an estimate derived from those prices, not a bill. They cover calls recorded in this machine's session logs; spend from another machine or another client (web, CLI) is not included. - With many stored sessions the first launch scans every log once (roughly a dozen seconds for two hundred sessions, in the background). After that it is incremental by file size, so a normal refresh is just a directory walk. - Logs live in `$DSH_HOME/sessions` by default (the `DSH_HOME` env var is followed automatically). If your own patch points `dsh-session-persistence-jsonl` at a different `root`, all four cost figures will read 0 — set the plugin's `sessionsRoot` to the same path. - Pure web UI plus HTTP routes, so it should work everywhere; mainly verified on the Windows desktop build. </details>