dsh-usage

🌊 dsh-usage

A persistent floating dock, a fully customizable balance / token-usage panel, an activity heatmap, and a dual-channel usage comparison for the DeepSeek Harness Web GUI (dsh web) and official Windows Desktop. See the host scope below.

✨ Feature tour 🌊 Persistent dock

Your key numbers stay visible at all times — balance glows green (red only when out of credit), rows are separated by hairlines, and a settings gear plus one-click refresh sit in the corner. When the sidebar collapses, the dock folds into a tiny balance pill. 🟢 Balance — green when healthy, red when drained 📊 Today / Month / Cache hit — glanceable token stats ⚙ Gear opens the panel · ↻ refresh re-queries instantly 🧲 Mirrors your pins — every change applies immediately

🎛️ Detail panel — all seven widgets

A two-column card layout; every widget has a detail and a compact form, and can be drag-reordered, collapsed, hidden, or pinned. 🎨 Everything customizable

Accent (presets + color picker), background, and panel opacity are adjustable live. Drag-reorder, pin, collapse, hide — every number presents your way, echoing DeepSeek Harness's "everything is a plugin" spirit.

At a glance UI supports Chinese and English. Balance requests resolve keys in memory through Harness's credential service; keys are not included in plugin caches or browser responses. Quick start

v0.4.0 supports DeepSeek Harness 0.1.x and 0.2.x, on Web and official Windows Desktop. Verified in a real desktop run on 0.2.1-rc.3 (the 0.2 path: open('read') handle, 85/87 sessions counted, endpoint 200); 0.2.2-alpha is untested. Live sessions are read through whichever Session API the host exposes (events, snapshotEvents, or ownEvents); persisted logs use readFrom (0.1.x) or the 0.2 read handle. A host that exposes no readable log API degrades to a reported skip instead of an HTTP 500 — it is not silently counted as zero. Real-machine 0.1.x verification is pending community retest; Desktop platforms other than Windows have not been tested on real machines.

Desktop uses the client platform: web contract, but installation belongs to the desktop profile and must use that app's bundled CLI while Desktop is fully quit. Open the app manually afterward; do not kill or restart it automatically. Update prompts select the active profile. Plugin appearance settings are origin-specific, even when profiles share DSH_HOME. Offline tests do not establish acceptance for every account, historical session, or Desktop feature.

Alternatively, use the fixed-name Release TGZ (available after publication; use a tag-specific versioned asset for a reproducible installation):

For Desktop, fully quit first and run this with that application's bundled dsh CLI, not the Web CLI: