@xavier711/dsh-deepseek-usage
DSH Web GUI 的 DeepSeek 使用情况面板：账户余额（官方 /user/balance API），以及按模型和工作区统计的本地会话令牌数据
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add @xavier711/dsh-deepseek-usage@0.4.3Deepseek Usage 以 @xavier711/dsh-deepseek-usage 发布，当前版本为 0.4.3。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
A DeepSeek usage panel plugin for the DeepSeek Harness Web GUI. It adds a 「Usage / 用量」 entry at the bottom of the left sidebar showing:
GET /user/balance (total, topped-up, granted).usage records) and shows: today / last 7 days / all time, a 7-day chart, today's token composition, per-model statistics, and per-workspace statistics (a workspace is the session's project directory; a collapsible panel expands each workspace into its own session records, and subagent sessions count toward their parent workspace).sessionPersistence seam the running harness exposes: the current snapshot-list + open(id,'read') handle API, or the older header-list + inspect() API. The panel no longer comes up empty on a newer harness.Note: DeepSeek's API does not expose an account-level usage endpoint (all candidate paths return 404 in practice). The usage data therefore comes from your local session logs — which contain the exact
usagevalues returned by the official API for every request.
The panel opens from the 「用量」 entry at the sidebar foot. All figures below are synthetic sample data — no real balance, keys, tokens, or session content.
| Dark theme | Light theme |
|---|---|
| Usage panel, dark theme | Usage panel, light theme |
You need Node.js first (download from nodejs.org).
Paste this into a terminal:
dsh plugin --profile web add git+https://github.com/xavier711/dsh-deepseek-usage.git#v0.4.3
Don't have dsh installed globally? Use this instead (npx downloads it on first run):
npx --yes @deepseek-ai/dsh plugin --profile web add git+https://github.com/xavier711/dsh-deepseek-usage.git#v0.4.3
Tip: if the installer complains that
pnpmis missing, runnpm install -g pnpmand retry.
git clone https://github.com/xavier711/dsh-deepseek-usage.git
cd dsh-deepseek-usage
./install.sh # auto-uses npx when dsh is not on PATH
dsh plugin --profile web add @xavier711/dsh-deepseek-usage
Ctrl+C in the terminal running dsh web, then run dsh web again (or npx --yes @deepseek-ai/dsh web).Because the package declares
dsh.bundle, the plugin row is activated automatically — no manual config editing.
Add a line to ~/.dsh/.credentials.yaml (replace sk-xxxx with your key):
DEEPSEEK_API_KEY: sk-xxxx
Or set the DEEPSEEK_API_KEY environment variable. Without a key, local usage statistics still work; the balance card just shows a hint.
dsh plugin --profile web remove @xavier711/dsh-deepseek-usage
Then restart dsh web and refresh the page.
The plugin never embeds an API key (no key material in the package). The key is resolved at runtime from the recipient's own machine — ~/.dsh/.credentials.yaml or the environment — and only on the host (server) side; the browser bundle never sees it. Safe to share.
lib/index.js host half — /dsh-usage/balance + /dsh-usage/local + /dsh-usage/period routes
lib/client.js browser half — sidebar action + panel (hand-built bundle, no build step)
cordis.patch.yml the plugin's own patch layer (dsh.bundle — auto-activated on install)
install.sh one-shot installer
Override row config by id in ~/.dsh/profiles/web/cordis.patch.yml:
- id: deepseek-usage
config:
balanceTtlMs: 60000 # balance cache TTL (ms)
maxSessions: 100 # most-recent sessions to replay
sessionConcurrency: 4 # parallel session-log reads
balanceTimeoutMs: 10000 # balance request timeout
localTtlMs: 30000 # local-usage cache TTL (ms); keeps signal-driven badge refreshes cheap
newPricingAt: 1786896000000 # peak/off-peak pricing effective date (2026-08-17 00:00 Beijing)
weekendOffPeakAt: 1787414400000 # weekends all-day off-peak rule effective date (2026-08-23 00:00 Beijing)
peakHours: [[9,12],[14,18]] # Beijing peak windows
# pricing: per-model rates (CNY per 1M tokens); an entry may carry
# eras: [{ at, peak, offPeak }] for rates that change from a
# moment on (2026-09-10 12:00 flash price cut, 2026-09-14 12:00
# V4 Pro billed as V4.1 Flash) — see the source repo
npm installs: run dsh plugin --profile web update @xavier711/dsh-deepseek-usage
(or re-add with the new version: ... add @xavier711/dsh-deepseek-usage@X.Y.Z).
Git installs: you installed a pinned snapshot, so updates are not automatic — but you
don't need to check for them: the plugin queries the GitHub releases feed
(hours-cached) whenever you open the usage panel and shows a 「New version
available」 banner with the exact update command. Simply run it, restart
dsh web, and refresh the page:
dsh plugin --profile web remove @xavier711/dsh-deepseek-usage
dsh plugin --profile web add git+https://github.com/xavier711/dsh-deepseek-usage.git#v0.4.3
I see dsh: warning: ... declares no dsh.bundle — installed as a plain dependency
You installed an older snapshot of the repository (pnpm caches git
dependencies by commit, so an install that happened before this package
declared dsh.bundle keeps the old version). Fix it by reinstalling from
the pinned tag:
dsh plugin --profile web remove @xavier711/dsh-deepseek-usage
dsh plugin --profile web add git+https://github.com/xavier711/dsh-deepseek-usage.git#v0.4.3
Then restart dsh web and refresh the page.
The 「用量」 entry does not appear after installing
Make sure the web server was restarted after the install (Ctrl+C in the
dsh web terminal, then run it again) and that you hard-refresh the browser
page (Cmd/Ctrl+Shift+R).
GET /dsh-usage/balance — { ok, isAvailable, currency, totalBalance, grantedBalance, toppedUpBalance, ... }GET /dsh-usage/local — { ok, sessionCount, errorSessions, pricing, buckets: { today, week, total }, days: [...7], models: [...], workspaces: [...], sessions: [...] } — each workspace entry is { path, name, sessionCount, subagentSessionCount, buckets: { today, week, total }, sessions: [...] } (sessions without a working directory group under path: null); each session row carries workspace and subagent (pricing includes newPricingAt, weekendOffPeakAt, peakHours)GET /dsh-usage/period — { ok, now, period: 'peak'|'offPeak'|'flat', range: [start, end] minutes-of-day, nextAt, nextPeriod, peakHours, weekendOffPeakAt, timezoneOffsetMinutes } — current Beijing peak/off-peak classification for the sidebar badge and the panel header; nextAt/nextPeriod describe the next actual period change (weekends skip to the next weekday's first peak start)