dsh-progress-summary
DeepSeek Harness 的带外进度播报：一个低成本辅助模型将实时推理转换为一行简短状态信息，适用于 Web UI 和 dsh-tui
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:tastynoob/dsh-progress-summary#81d931fc0205e6363b9157bcb6a5378bc260100cProgress Summary 以 dsh-progress-summary 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Out-of-band progress narration for DeepSeek Harness: a cheap auxiliary model turns the live chain of thought into one short status line, shown above the composer in the Web UI and on the dsh-tui status line.
The transcript's four work-details modes are untouched; this plugin does not add a fifth mode.
Codex-style progress text comes from a model-side channel (reasoning.summary plus commentary
messages). DeepSeek exposes only raw reasoning_content, so there are two ways to approximate it:
The cost is an extra call; the benefit is that the task never competes with its own status text.
Two layers: free lines update at every boundary, model lines fire only before a tool call.
| Trigger | Output | Cost |
|---|---|---|
| Turn start (opt-in) | "Analyzing the request" | 0 |
| Every tool call (opt-in) | a line derived from the tool name and arguments | 0 |
| Before a tool call, with both floors met | one sentence from the auxiliary model | 1 call |
| Turn end | idle, clearing both surfaces | 0 |
The model line requires both:
minIntervalMs since the last model line (default 20s).minTokens of new reasoning since then (default 600; charsPerToken
defaults to 3, so roughly 1800 characters).A tool call is the only trigger that starts a model line because it is the one point where the preceding chain of thought is known to be complete: the model has committed to an action. A pause in the stream proves nothing (network jitter, a provider that emits two tokens and stalls, ordinary tokenization gaps), which is why there is no timer-based trigger.
Below either floor the material stays buffered and the next tool boundary re-checks. A failed call returns the consumed characters and retries at the next boundary. Turns without tool calls get no model line at all — a deliberate trade: rather than cut into a reasoning block, stay quiet.
The two free rows are off by default (quickLines: false): the dock is a summary surface, not a
second command log. The prompt also forbids naming tools, commands, or paths, because the
transcript already shows every call.
Caps: maxPerTurn (default 40) calls per turn, 96 output tokens per call, effort=off.
dsh plugin --profile web add "github:tastynoob/dsh-progress-summary#v0.1.0"
dsh plugin --profile dsh-tui add "github:tastynoob/dsh-progress-summary#v0.1.0" # optional
dsh plugin add forwards the spec to pnpm, so any pnpm git form works:
github:user/repo#tag, git+https://github.com/user/repo.git#tag, or the plain
https://github.com/user/repo#tag. The tag pins the version; the package has no build step, so
pnpm clones it and installs its dependencies from the registry.
dsh plugin --profile web add dsh-progress-summary
dsh plugin --profile dsh-tui add dsh-progress-summary # optional: TUI
The package declares dsh.bundle.patch, so dsh plugin add appends it to the profile's bundle
list; cordis.patch.yml inserts the progress-summary row and dsh.client makes the Web client
load the browser half. The plugin deliberately depends on no DSH core package: the session
module and the record-append function come from the Loader's own module instance at runtime, so
installing it can never shadow the host's core packages with different versions.
Remove with dsh plugin --profile web remove dsh-progress-summary.
link:)npm install --omit=dev
dsh plugin --profile web add "link:$PWD"
link: is a development convenience: the profile holds a symlink, so a source edit plus a restart
is enough. It has no bearing on publishing.
| Key | Default | Meaning |
|---|---|---|
enabled | true | Master switch; also the Settings toggle (live) |
provider / model | auto | auto follows the session's own route; otherwise pin a route |
effort | off | Reasoning effort for the auxiliary call |
maxTokens | 96 | Output cap for one line |
timeoutMs | 8000 | Abort a single call after this long |
minIntervalMs | 20000 | Time floor between two model lines (live) |
minTokens | 600 | Token floor at a tool boundary (live) |
charsPerToken | 3 | Divisor used for the token estimate |
excerptChars | 700 | Reasoning tail sent to the model |
maxLineChars | 128 | Hard cap for the rendered line (characters) |
maxPerTurn | 40 | Hard cap on auxiliary calls per turn (live) |
lang | auto | auto follows the host locale; zh / en pin it |
publish | true | Commit ignorable records so the Web UI receives lines |
tui | true | Contribute the line to a composed TUI |
quickLines | false | Opt into the free turn-start/per-tool lines |
subagents | false | Narrate subagent sessions too |
debug | true | Append a bounded diagnostics log under |
Fields marked live are volatile: a save takes effect on the next tool boundary, without a restart.
plugin:progress-summary/line (an ignorable record, safe for resume),
which folds into the progressSummary session projection. The browser reads it with
useProjection; nothing is written to the model-visible history.ctx.tuiStatus.set('progress-summary', line), cleared at turn end. This path does
not need the record at all.Both profiles load the same package; only the available services differ.
session/event listeners run inside the session's own
commit, where a second append is refused as re-entrant.@deepseek-ai/dsh-session
(entry.moduleNamespace), because path-resolved copies are separate ESM instances whose private
Session brand does not match the live session objects.request/header route, so no separate
credentials or model catalog entry is needed.publish: false to keep the log clean, at the cost of the Web line.npm test # node --test, 35 cases
npm run check # syntax check of every runtime file
~/.dsh/