@dsh-external/dsh-session-turn-eta
根据步骤历史预测当前 DeepSeek Harness 回合的剩余耗时，并在编辑器下方以带实时百分比的进度条显示。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:778672151/dsh-session-turn-eta#9fd24ffe8867c1882728672e8b05607d231efa34Session Turn Eta 以 @dsh-external/dsh-session-turn-eta 发布，当前版本为 0.4.1。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Live remaining-time prediction for the current DeepSeek Harness turn, shown as a progress bar with a live percentage under the composer.
~12m 34s left / 约剩 12 分 34 秒).
The percentage ticks locally while the turn is open. The filled track ends in
a leading dot and carries a slow shimmer.dsh plugin --profile web add github:778672151/dsh-session-turn-eta
The repository ships a prebuilt lib/, so installing does not run a build step.
Restart dsh web if the profile asks for it, then send any message: the bar
appears under the input box while the turn runs.
| DeepSeek-Harness desktop | 0.2.1-rc.5 (type-checked against its published packages) |
@deepseek-ai/cordis | >=4.0.5 <5 |
@deepseek-ai/dsh-session | ^0.2.1-rc.1 |
@deepseek-ai/dsh-session-projection | ^0.2.1-rc.1 |
@deepseek-ai/dsh-client-ui-conversation / dsh-client-locale | ^0.2.1-rc.1 (client half, optional peers) |
| Node | >=22 for building; the shipped bundle runs on the DSH host |
The host half registers one turnEta session projection and nothing else:
it folds the durable turn/start, step/start, step/end and turn/end
events into a prediction. The projection registry already drives every
registered unit once per committed event, so the plugin does not replay
session/event a second time; it only mirrors the registry's change feed
(onChanged, which fires when the published view changed by Object.is) onto
two typed Cordis events: turn-eta/update while a turn is open and
turn-eta/complete once per turn.
8 x median), so the rate tracks the steps that dominate a turn while a
single 9-hour idle gap still cannot drag it up.The client half reads that projection through the standard useProjection seat
and renders it on the conversation.composer.dock slot. The plugin never
mutates the session and registers no model-visible capability.
The bar ships five skins: auto (harness theme tokens, the default and the only
one that follows light/dark automatically), bilibili, mint, sunset, and
ocean. A skin only owns the fill gradient, the leading-dot glow, the track
tint, and the celebration colour; layout and accessibility never change.
Pick one either per render or document-wide:
// per render (the dock entry accepts an optional `skin` prop)
<TurnProgress skin="bilibili" ... />
<!-- document-wide, e.g. in the host page or a user script -->
<body data-turn-eta-skin="ocean">
The client entry exports TURN_ETA_SKINS, TURN_ETA_DEFAULT_SKIN,
TURN_ETA_SKIN_ATTRIBUTE, isTurnEtaSkin() and resolveTurnEtaSkin(). Unknown
values fall back to auto. All motion (shimmer, pulse, celebration) is disabled
under prefers-reduced-motion: reduce.
The fold is plain data in, plain data out: the same code the bar renders from can be driven without Cordis, a session, or the plugin instance.
import { createTurnEtaFold, etaCore, ETA_TUNING } from '@dsh-external/dsh-session-turn-eta'
// full fold: the projection the client renders
const fold = createTurnEtaFold()
for (const event of durableLog) fold.apply(event)
const { remainingMs, predictedTotalMs, method } = fold.view()
// or just the math, from whatever facts you already have
const core = etaCore({ startTime, stepDurations, completedTurnSteps, stepSamples, asOf })
createTurnEtaFold(seed) accepts a captured state() so a fold can continue
from a projection checkpoint instead of replaying the whole log. ETA_TUNING
exposes every constant (RATE_PERCENTILE, REANCHOR_AT, OUTLIER_CAP, …) so a
consumer can read the calibration instead of copying numbers.
The projection runs on every committed session event, so the fold is written to cost O(1) amortised per event rather than O(history) per event:
withSample), so sorting is never repeated for one append;Measured with npm run bench on Node 24 (per-event cost of the fold alone, no
registry, no UI): 12.9k events over 8 turns of 50 steps run at ~245k events/s,
up from ~9.5k events/s before these changes; the cost stays flat as the history
grows (32k events over 80 turns: ~150k events/s).
npm run test:equiv fuzzes the optimised primitives against the reference
formulas (9,300 comparisons) so the speed-ups cannot drift from the maths.
The published bundle is built by tsdown (no monorepo checkout required):
npm install
npm run build # -> lib/index.js (host) + lib/client.js (client)
npm test # host estimator invariants + client render states
npm run typecheck checks both halves against the published 0.2.1-rc.x
contract: the host half (tsconfig.json) against dsh-session /
dsh-session-projection, and the client half (tsconfig.client.json) against
dsh-client-ui-slots / dsh-api-session-controller / @types/react.
scripts/build.sh is an optional development helper that links a contract tree
(DSH_CONTRACT_DIR, defaulting to a local copy of the published packages) and
type-checks both halves, so the build and the desktop app agree on the same
contract instead of on whatever a monorepo checkout happens to contain.
MIT