bowenliang123/dsh-context v0.59.1 on GitHub

Install / Update

Install the dsh-context plugin on DeepSeek Harness with released NPM package:

dsh plugin --profile web add dsh-context@latest

Update the dsh-context plugin:

dsh plugin --profile web update dsh-context@latest

Custom or aliased gateway providers now price deepseek- model ids against DeepSeek's own listing (#93). A provider id outside the models.dev registry (a self-hosted gateway, a sub2api-style relay) falls back to resolving prices by model id across the whole registry — where Azure's self-named SDK package could win deepseek-v4-pro and its flat listing (no cache price published) billed cache hits as plain input at 4× the official rate. A deepseek- model id now prices from DeepSeek's own registry branch first, cache rates included, and still falls back to the model-side tiers when the first party does not list the id.

The cost tooltips now name the resolved mapping. The cost and subagent-cost tips render a per-model price table — non-zero bucket rates at two decimals — with each block closed by a listing line naming the models.dev provider id · model id the rates resolved from (e.g. deepseek · deepseek-flash), so an aliased route shows exactly which listing prices it. Zero list prices drop their rows, and the peak-window and CNY-conversion notes appear only when they apply.
The cost cell opens the models.dev provider listing. When one provider priced the whole scope, the cell is clickable and opens https://models.dev/providers/<provider id>/ in a new tab; a multi-provider scope stays unlinked and names each face in the tooltip instead.

feat(stats): open the models.dev provider listing from the cost cell (94db113)
feat(stats): revamp the cost tooltip around the resolved listing face (1b1c811)
fix(cost): price deepseek- model ids from the first-party branch first (ee236f2)
chore: release v0.59.1 (49b7af5)