dshseek

seek://news/dsh-tui-v0-18-0

dsh-TUI 0.18.0: Validation Line at rc.5 (Nov 1, 2026)

Nov 1, 2026release#release #dsh-tui #clients← All news

TL;DR

dsh-TUI 0.18.0 reached npm at 03:43 UTC on 2026-11-01, eight days after 0.17.0. Per the release notes, PR #1806 moves the validated DSH line to 0.2.1-rc.5 — until now the host's plugin compat check refused to load the TUI after an upgrade past rc.3 — while onboarding gains first-step sign-in and /plugin list gains the official create_worktree switch.

dsh-TUI 0.18.0 Takes the Validation Line to rc.5 Eight Days After 0.17.0 — the Release That Lifts the Post-Upgrade Refusal to Load, Adds First-Step Sign-In and Ships the Official Git Worktree Switch.

The DSH v0.2.1-rc.5: Thinking-Content Fix (Oct 30, 2026) coverage ended with the harness itself; this is the ecosystem side of the same version numbers. dsh-TUI, the fullscreen terminal client, published 0.18.0 to npm at 03:43:39 UTC on November 1 — eight days after 0.17.0, and aimed straight at the compatibility wall that the harness’s rc.4 and rc.5 raised for it.

The refusal, and the line that fixes it

Per the release notes, the mechanism was the host’s plugin compatibility check: v0.17.0 declared support only up to DSH 0.2.1-rc.3, so when the DSH npm package moved on to rc.4 and rc.5, upgrading the host left the TUI refusing to load. PR #1806 (merged 2026-10-30, by the same @AdamPlatin123 who filed the onboarding PR below) moves rc.4 and rc.5 into the validated line and peer range, with the dst automation adapter’s validated versions following. The release also states its own evidence for calling the move low-risk: comparing the published packages file by file, the upstream code the TUI uses changed only in version numbers between rc.3 and rc.5, so the host replica fingerprint is unchanged. That comparison is the release’s claim, quoted as such — this article verified the stamps and the merges, not the byte comparison.

First-step sign-in, and what it feeds

The second headline change is onboarding. Per the notes, the first launch step can now sign in to the subscription account or add a model provider — the latter reusing the /provider wizard — before the terminal itself matters, and can re-check or skip the step. Subscription sign-in brings models back, and the release spells out the adoption choice as 0/1/N: report the results only, set a model as default directly, or pick one in an inline selector. The /provider wizard’s switch question, per the notes, lists the models the sign-in enabled item by item and keeps a keep-current-model option.

The official worktree switch, and grants that follow the plugin

Two quieter changes round out the feature set, per the notes. /plugin list now exposes DSH’s official create_worktree experimental tool (PR #1745, merged October 24): the tool card titles the branch name and reports the checkout location and start point in two lines. The Minimal preset and the bundled liangshen preset do not offer the tool — Minimal’s persistent shell does not follow directories — and worktrees are not cleaned up automatically; branches need deleting separately. Plugin grants, meanwhile, follow the lifecycle (PR #1747, merged October 26): grants are issued per the package’s own declarations on install or enable, revoked on disable, and deleted on uninstall, so a later package reusing the same component id does not silently inherit what an earlier one was granted. The /plugin enable confirm page lists the declared permissions row by row and collapses to the terminal height; Esc abandons the enable. One more behavior change rides along: @~/… now resolves to the home directory at any depth, matching the shell, with a workspace directory genuinely named ~ written as @./~/… (PR #1739).

The contract going forward

Per the notes, 0.2.1-rc.5 is the main adaptation line; rc.4, rc.3, rc.2, 0.2.0-rc.1, 0.2.0-rc.2 and earlier stay in contract, and anything outside it draws a drift warning. The release addresses the users the bug already locked out: the in-app /update needs the TUI to open, so the notes point them at the npm upgrade command directly and state that dsh plugin allow-version exemptions granted to v0.17.0 are no longer needed after upgrading. The Windows offline installer follows the contract to rc.5 and upgrades an rc.4 host rather than downgrading it to rc.3, which the notes say v0.17.0’s installer did.

More in this series

Official references