dsh-account-balance：在 DSH 侧栏底部常驻显示 DeepSeek 账户余额与花费
@lithane/dsh-account-balance 是 Lithane 维护的 DSH 客户端插件，在侧栏底部常驻显示 DeepSeek 账户余额与今日花费，点击可展开最近提问与会话/工作区等多层级成本明细。余额优先走 DSH 内置 deepseekAccount，无需 API Key；成本由本地会话日志估算。支持峰谷时段、定价自动同步与 account_balance 模型工具。安装可用 dsh plugin --profile web add @lithane/dsh-account-balance，需 Node ≥22.15，peer @deepseek-ai/dsh <0.3.0。MIT，基于 dsh-balance-widget 独立演进。
Read Moredsh-account-balance: DeepSeek and OpenRouter Dual Account Balance Monitoring Plugin
The DSH dual-account balance monitoring plugin is maintained by its developers and designed to address the challenge of managing both DeepSeek and OpenRouter balances simultaneously. It provides a persistent chip in the web interface header, supporting dual-source balance display, automatic refresh, and fault tolerance. Data is securely stored in the host environment and decoupled from the core version. The plugin is easy to install and suitable for developers who need convenient monitoring of dual-account balances.
Read MoreDeepSeek Harness Web Dual-Account Balance Chip
`dsh-account-balance` is a DeepSeek Harness plugin designed to address the challenge developers face when monitoring both DeepSeek and OpenRouter balances. It provides a persistent chip in the session header that displays dual-account balances in real time (format: ¥xx.xx · $xx.xx). Users can hover to view a detailed breakdown. It features fault tolerance, automatic refresh every 3 minutes, and security isolation. The plugin retrieves data through host-side APIs and renders components on the client side, with a decoupled core so upgrading DSH core does not require reinstallation.
Read Moredsh-account-balance: DeepSeek Account Balance Dashboard Plugin
The DSH Web client plugin `dsh-account-balance` integrates DeepSeek account balances into the chat interface in real time, avoiding frequent page switching. The plugin works through Host and Client component collaboration, proxies the official API to fetch data, and provides features such as hover-to-view details and automatic refreshing every 60 seconds. Its security mechanism ensures that the API Key remains only in local processes. Users do not need additional configuration; they can use it immediately after installation and service restart, making it suitable for developers who need to monitor balances frequently.
Read More