DSH 0.2.2-rc.2: Worktree Review, Named SubAgents, DeepSeek Search by Default (Nov 11, 2026)

Seven calendar days after the line’s first candidate comes the second: per the releases API (fetched 2026-11-11), dsh-v0.2.2-rc.2 was published at 11:33:06 UTC on November 11 with the pre-release flag set — DSH 0.2.2-rc.1: First Release Candidate Aggregates the 0.2.2 Line (Nov 4, 2026) covered rc.1, whose tag page stamps 2026-11-04 13:07 UTC. Where rc.1’s notes opened with a sentence saying they summarized the major user- and developer-facing changes since v0.2.1-rc.5, the rc.2 notes carry no summary sentence and go straight to four sections; the Full Changelog link at their foot compares dsh-v0.2.2-rc.1 with dsh-v0.2.2-rc.2. Each section holds the same number of items in the English and the Chinese half, counted separately: three, twenty-seven, twenty-six and twenty.

New Features: three

Per the release notes, New Features holds three items. Git Worktree supports reviewing changes by branch, commit and file category, with GitHub reviews, synchronized viewed-file progress and branch updates directly in DSH (@LegGasai). SubAgent supports named, multi-level collaboration, while AgentTeam can be enabled per session with a shared member and task panel (@Dudu-0223, @Yifffan). And Desktop settings now let users switch between stable and development update channels (@winewill). By the same per-locale count, rc.1’s New Features list held thirteen items.

Improvements: twenty-seven

The Improvements section holds twenty-seven items, per the notes. Around review and agents: commenting, file navigation and narrow-screen layouts during code review, less lag when viewing large changes and more time allowed to create worktrees in large repositories; browsing and coordinating nested subagents, with task descriptions prioritized, incremental expansion and retries after failed reads; and Agent terminals made visible in the sidebar, where users take over by typing — the notes add that user-terminal content agents are permitted to read enters model context and session records. In chat: earlier messages load automatically when scrolling up, with reading-position stability prioritized; workspace instructions, skill catalogs and other context received by the model can be expanded for inspection; code diffs gain added and removed row colors and per-file syntax highlighting; and a transient request failure can be recovered with Continue generating instead of another message.

On the model side, retry conditions, counts and wait times become configurable in model settings, saved API keys show as masked previews with full replacement or removal, a web-search call supports up to 10 queries and 10 sources by default, and more read-only tools run concurrently while returning results in call order. The sidebar gains name and path file search with exclusion rules and hidden-file controls, and infrequently used plugin entries can move into More and be restored without changing their original order. One item carries work for extension authors: menus stay aligned with their triggers during page zooming, panning and long-list browsing, and custom panels need to adopt the new positioning API.

Bug Fixes: twenty-six

Per the release notes, Bug Fixes holds twenty-six items. Several concern plugins: an optional plugin’s failure no longer prevents the entire Web app from starting, while required-plugin failures remain visible errors; enabled but unloaded plugins show Not running and the reason instead of appearing to run; and private Git plugin details load for users with SSH-only credentials.

Several concern model connections: on Anthropic Messages connections, invalid signed thinking is omitted after history-prefix changes, to reduce persistent request failures after compaction; some model-gateway failures are no longer misreported as invalid API keys, so retries follow the actual response status; some models no longer reject further requests after tools are removed or replaced in a session; and startup no longer fails after configuring DeepSeek endpoints in the DSH user directory — the notes add that project environment settings still cannot override these endpoints.

Session handling: retried requests during message submission or attachment preparation no longer submit the same message more than once; some errors during task cancellation or session shutdown no longer leave work running or release resources prematurely; history loading and new-message displays no longer stay stuck after a chat-update error; and repeated waits for subagent messages within PTC no longer wake repeatedly for the same message. Platform-side, the list covers accumulated authentication data preventing Desktop startup after repeated launches, welcome-screen confirmation failing to save when the Windows CLI is launched through a short path, mobile Safari enlarging chat text beyond the configured font size when unfolding or changing the viewport, long-running background processes slowing session loading and creation on Linux, progressively slower loading when browsing multi-page PDFs, and inspecting large Cordis trees potentially terminating the service when snapshots approach the size limit.

Chores: twenty, many asking integrators to act

Per the release notes, Chores holds twenty items, and many of them end in a migration instruction. Several change default behavior. Web search now defaults to DeepSeek Search API, with separate account or API-key billing choices for Search and Fetch; older providers and custom settings migrate using the upgrade guide. Archiving sessions cleans up eligible Git worktrees by default while preserving branches and commits; disabling cleanup retains local directories, and custom configuration and Forge plugins migrate. AgentTeam uses unified named subagents with the interrupt tool disabled by default; custom plugins and SDK integrations migrate, and all processes sharing session storage upgrade together — while SDK configuration can enable Team collaboration by default for new sessions, preserving the saved choice when resuming existing ones.

For plugin and extension authors: plugins can dynamically register and remove MCP servers, query their status, restart them and probe connections, without requiring users to maintain each server configuration manually; plugins can extend chat code-block rendering by language, falling back to ordinary code blocks when no renderer matches or rendering fails; plugin indexes can provide GitHub stars and weekly npm downloads while keeping the order supplied by the index as the default; Creator guidance consolidates into dsh-doc, and extensions referencing old skill names or paths need migration; tool failures provide clearer error types and codes, and plugins and SDK integrations relying on older classifications need updating; Session supports batched event appends without changing the log format, and custom append wrappers need to support batch calls; and account notifications support announcements and refresh with the interface language — existing sign-ins are retained, while custom account plugins and configuration need migration.

Some items state an access boundary. Office uses native tools, with skills available in Web and SDK sessions and old packages and skills to migrate; the notes add that document parsing runs in the DSH host process outside the shell sandbox. LiveShare’s multi-session sharing and plugin authorization are adjusted and old grants need reconfiguring; the notes add that PTC can access files outside the shared directory, so share only with trusted people. Windows extra-directory grants apply only to file tools, not terminal or PTC access, and related sandbox extensions need migration.

The rest: custom model providers support the native Gemini API, including model discovery and reasoning-level settings; model-request User-Agent headers include the active profile, helping servers distinguish Desktop, Web, CLI and SDK requests; PTC limits total tool calls according to its runtime budget, and exceeding the limit terminates the code and clears retained state without undoing completed operations; Computer Use window operations, keyboard control and authorization are adjusted, keeping the system pointer still by default, with custom scripts and helpers to upgrade together; npm installations and Desktop include matching source code and documentation, which Python single-file runtimes exclude; and Zod moves to 4.6.6 and Stagehand to 4.4.0, where Stagehand automatically discovers extensions and the old extensionId setting no longer takes effect.

npm at fetch time

Per this site’s read of the npm registry on 2026-11-11, @deepseek-ai/dsh listed no 0.2.2-rc.2 version: the version endpoint answered 404, and the dist-tags latest and next both read 0.2.2-rc.1, which the registry stamps as published at 09:20:32 UTC on 2026-11-04; the alpha tag read 0.2.2-alpha.3. The release record itself lists no assets. That is a dated observation about one read, not a statement about when an npm publish follows — the notes do not address it.

New Features: three

Improvements: twenty-seven

Bug Fixes: twenty-six

Chores: twenty, many asking integrators to act

npm at fetch time

More in this series