Proton1917/dsh-live-stats

Live token estimates and true streaming TPS for DeepSeek Harness Web

Renders the DeepSeek Harness composer stats row with live token counts and a throughput line. It shows input, output and unabridged total tokens — a leading ~ marks a value that still includes the current request's input estimate — and adds a second row with tokens per second, computed as tokens added after the first output sample divided by the elapsed time between the first and latest token-bearing stream events. Streamed DeepSeek output is counted with the official tokenizer, provider usage replaces the provisional values when it arrives, exact cache accounting still comes from DSH's durable token-usage projection, a retry replaces the prior estimate for that step, an aborted turn removes its unsettled estimate, and a one-sample response shows no TPS value instead of an artificial rate.

uncategorized ★ 1 updated 2026-08-13 ❌ failed test
View on GitHub ↗

Install

dsh plugin --profile web add @proton1917/dsh-live-stats@link:$HOME/Projects/dsh-live-stats
dsh web

README's 'Load in DSH Web' block quoted verbatim: the link: form points the profile at a local checkout, so substitute your own checkout path, and the README's build-and-test step runs first. Registry check 2026-09-17: @proton1917/dsh-live-stats returned 404 on npm, so no published version is asserted and the local-link form is the route the README documents.

Compatibility

README: it replaces the built-in conversation.composer.dock entry through the slot registry's documented same-id priority mechanism and reads the public sessionStats and tokenUsage projections, owning liveTokenUsage itself — so it leaves the harness checkout untouched and a harness update no longer needs a StatsLine source patch. The README publishes requirements, a compatibility-updates section and a build/test step, and notes streamed output is counted with the official tokenizer.

Details

Recent updates

The README documents the counting rules, the slot it replaces and the compatibility-update path rather than a release-by-release table.

FAQ

How do I install it?
The README's block is dsh plugin --profile web add @proton1917/dsh-live-stats@link:$HOME/Projects/dsh-live-stats followed by dsh web — a link: install that points the profile at your local checkout (that npm name returned 404 on 2026-09-17).
How is tokens per second calculated?
Per the README, TPS is tokens added after the first output sample divided by the elapsed time between the first and latest token-bearing stream events; final usage and block-end events correct counts but do not extend that interval, and a one-sample response shows no TPS at all.
Does it modify the harness?
No — the README says it replaces the built-in composer dock entry through the slot registry's same-id priority mechanism, reads public sessionStats/tokenUsage projections, and leaves the harness checkout untouched.

More plugins in uncategorized

Browse more in uncategorized

Guides for uncategorized plugins