dsh-terminal-startup-bar
DeepSeek Harness（dsh）的终端启动状态栏：显示启动过程正在加载哪个插件、已耗时多久以及进度如何。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:fishOfOUC/dsh-terminal-startup-bar#6fcb377c64f1ae7528145c8fe8f48a3e5c204e7aTerminal Startup Bar 以 dsh-terminal-startup-bar 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
A terminal startup status bar for DeepSeek Harness (dsh).
A booted dsh profile mounts dozens of plugin rows and loads them concurrently. On a cold start with a large composition that means the terminal sits silent for ten or twenty seconds with no way to tell whether anything is happening. This plugin turns that silence into one line:
⠋ 正在加载 @deepseek-ai/cordis-plugin-timer… 3.2s 36/140
⠹ 正在加载 @deepseek-ai/dsh-session-projection-cache… 7.2s 130/142
⠸ 正在加载 @deepseek-ai/dsh-workspace… 8.3s 136/142
⠸ 正在加载 @daweifu/capability-menu/policy… 8.4s 141/142
✔ 启动完成 (8.7s)
The line names the plugin that has been outstanding longest, how long the boot has been running, and how many plugin rows are up. It is replaced by a completion line when the Loader settles, and it is erased — never left behind — on failure or teardown.
A local dsh plugin lives at $DSH_HOME/local-plugins/<name> and is wired into a profile as a link: dependency plus one entry in dsh.profile.bundles. That is how dsh finds an out-of-tree plugin without going through a registry.
git clone https://github.com/fishOfOUC/dsh-terminal-startup-bar \
"$DSH_HOME/local-plugins/dsh-terminal-startup-bar"
$DSH_HOME resolves to ~/.dsh unless the environment sets it.
In $DSH_HOME/profiles/<profile>/package.json, append the name to dsh.profile.bundles and add the dependency. Bundle order is application order, so listing it last is enough — the row it inserts has no dependencies on other plugins.
{
"dsh": {
"profile": {
"bundles": ["@deepseek-ai/dsh-base", "@deepseek-ai/dsh-web-app", "dsh-terminal-startup-bar"]
}
},
"dependencies": {
"dsh-terminal-startup-bar": "link:/absolute/path/to/.dsh/local-plugins/dsh-terminal-startup-bar"
}
}
node_modulespnpm install in the profile directory creates this from the link: dependency. To do it by hand:
ln -s "$DSH_HOME/local-plugins/dsh-terminal-startup-bar" \
"$DSH_HOME/profiles/<profile>/node_modules/dsh-terminal-startup-bar"
New-Item -ItemType Junction `
-Path "$env:DSH_HOME\profiles\<profile>\node_modules\dsh-terminal-startup-bar" `
-Target "$env:DSH_HOME\local-plugins\dsh-terminal-startup-bar"
Confirm the wiring without booting anything — the row must appear in the composed tree:
dsh web --dump-config | grep -A1 terminal-startup-bar
dsh plugin --profile web add dsh-terminal-startup-bar
Then add "dsh-terminal-startup-bar" to dsh.profile.bundles as above. The package ships cordis.patch.yml, so no patch file of your own is needed.
To mount the plugin from a package that is already a dependency, without listing it as a bundle, put the row in $DSH_HOME/profiles/<name>/cordis.patch.yml yourself:
- insert:
- id: terminal-startup-bar
name: dsh-terminal-startup-bar
config:
label: Loading
--patch overlays resolve a relative plugin name against the overlay file's directory, so a working tree can be mounted directly. examples/local.patch.yml does exactly that:
dsh web --patch ./examples/local.patch.yml --port 3081
Every key is optional. An unknown key, or a value of the wrong type, throws at load with the key named rather than being ignored.
| Key | Type | Default | Meaning |
|---|---|---|---|
enabled | boolean | true | Keep the package installed but silent. |
stream | 'stderr' | 'stdout' | 'stderr' | Which standard stream the bar paints on. |
intervalMs | integer ≥ 16 | 80 | Milliseconds between repaints. |
frames | string[] | ⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏ | Spinner frames, cycled in order. |
label | string | 正在加载 | Text before the plugin being loaded. |
readyLabel | string | 正在完成启动 | Text used once every plugin is active but the launcher has not committed readiness. |
doneLabel | string | 启动完成 | Text on the closing line. |
showElapsed | boolean | true | Show elapsed seconds. |
showProgress | boolean | true | Show done/total plugin rows. |
showCompletion | boolean | true | Print the closing line on a successful boot. |
force | boolean | false | Paint even when the target stream is not a terminal. |
An English composition:
- id: terminal-startup-bar
config:
label: Loading
readyLabel: Finishing startup
doneLabel: Ready
The bar writes nothing at all when its stream is not a TTY, unless force is set. That is what keeps spinner frames out of CI logs, captured output, and supervisor pipes.
ctx.get('loader'). total counts enabled plugin rows; group rows, disabled rows, and nested-tree carriers (the root cordis:include, whose duration is the whole boot by construction) are excluded. done counts rows whose fiber reached the active state, and the named subject is the first row that has not, in composition order.Promise.allSettled, so rows start concurrently; there is no single row that is "the one loading". Naming the longest-outstanding row is the reading that stays truthful under that concurrency, and it advances as earlier rows finish.loader.envData.startTime is stamped before the first profile row mounts, so elapsed time covers the whole boot. A missing, non-numeric, or future stamp falls back to the moment the row applied.appReady signal is a second stop for compositions whose Loader settles differently. The row's own effect owns the repaint timer, so disposal — a failed boot, a signal, an HMR reload — always erases the line.@deepseek-ai/cordis: it reads the two facts it needs — the entry list and one fiber state — structurally. A loading indicator that pulls in its own module graph would be measuring a startup it slowed down.dsh boots quietly in practice, and the bar stops at Loader settle — before the Web app prints its URL — but a row that logs during startup can still be clipped.readProgress compares against FiberState.ACTIVE's numeric value rather than importing the enum, which is what keeps the plugin dependency-free. A future Cordis release that renumbers the enum would need this constant updated.npm test # node --test, no dependencies and no install step
The suite covers the pure formatter, the Loader tree reader, config validation, the bar's paint/erase lifecycle under an injected clock and timer, and the plugin's wiring against a context double.
MIT