DSH Desktop2.0.22-next

This Next update upgrades the upstream to the candidate release DeepSeek Harness v0.2.2-rc.1, while also introducing the new macOS Computer Use (dsh-cua-bundle), OAR Subagents, LiveShare, and one-click updates for third-party plugins; adding the in-account embedded top-up and usage pages, right-click Save As, and dragging image files out; and fixing issues including failed Windows sandbox commands and Host exiting while idle.

DSH NEXT is a community-maintained open-source project, not an official DeepSeek product.

Upstream version: DeepSeek Harness v0.2.2-rc.1.

Breaking upstream kernel update (dsh v0.2.2-rc.1)

This upgrade to DeepSeek Harness v0.2.2-rc.1 includes breaking changes to kernel interfaces and runtime behavior, which may affect third-party plugins and self-deployed environments: - Third-party and custom plugin compatibility: The upstream has been upgraded to Cordis 4.1.0, which refactors step-based tool activation, separates native and PTC tool execution, fixes model routing, and changes the asynchronous session projection interface; the formerly independent “Git Worktree” plugin has been merged into “Change Requests & Worktrees.” Third-party plugins not yet adapted to 0.2.2 may cause startup failures. They can be updated／disabled in the Recovery Assistant through Safe Mode or “Plugins → Installed”; official components installed on demand in older versions will be automatically cleaned up before startup and can be installed again by re-enabling them on the “Plugins” page. - Self-deployed PTC and remote SSH upgrade requirements: The PTC control channel now uses birpc, the SSH protocol has been upgraded to v3, and execution status codes have been replaced with ABORTED; self-deployed bootstrap or remote SSH helpers must be upgraded in sync with 0.2.2-rc.1. - Runtime environment and default policy changes: The minimum Node.js version for running DSH externally has been raised to 24.9 (the desktop installer already includes Node 24.21); for custom models without declared capacity, the default context／output has been changed to 1M / 128K; pre-reading before file modifications and external modification checks are disabled by default; web_fetch now allows access to proxies and private network addresses by default.

New and improved - New macOS Computer Use (dsh-cua-bundle) and dual-version switching: On macOS, dsh-cua-bundle can be downloaded and installed on demand, and a toggle is provided on the Computer Use (Next) details page (macOS 14+ supported, for PTC mode); once enabled, it automatically takes over and hides the commands and tools of Computer Use (Next) in PTC sessions, and switching does not require a restart. - OAR Subagents, LiveShare, and plugin management: OAR Subagents (which can delegate independent tasks to local Claude Code or Codex and configure default permissions), LiveShare (experimental), Ralph, and Session Search are now available on the Plugins page; “Plugins → Installed” supports checking for new versions of third-party marketplace plugins and updating them with one click. - Upstream 0.2.2-rc.1 features and native desktop integration: Supports quoting selected chat text, copying the complete session as Markdown, collapsing steps while retaining all assistant text replies, uploading images as soon as they enter the input box, globally unified right-click and keyboard menus, keeping file previews in the directory tree, and host-level “Automated Tasks” management; the desktop client now includes embedded in-app views for account top-ups and usage, native right-click “Save As” and cross-origin image copying, and directly dragging sessions and preview images out as files. - Linux update checks, CLI, and “Open With”: The Linux version supports checking for updates and opening the download page, and supports directly running the built-in CLI through <app> dsh <arguments>; Windows “Open With” now recognizes Windows Terminal and applications under paths containing Chinese characters, while Linux now also recognizes Ptyxis and GNOME Console.

Fixes - Windows sandbox and encoding compatibility: Fixed commands exiting without output under the Windows restricted sandbox, errors after temporary directories were cleaned up by the system, and the issue where running dsh commands in the tray terminal mistakenly launched a second desktop window; the application installation directory can no longer be selected as the workspace or data directory; fixed garbled Chinese text when pwsh invokes Python and the issue where configuration files containing a UTF-8 BOM caused entry into the Recovery Assistant. - Host stability and recovery diagnostics: Fixed an issue where timeouts in background bridge calls during idle periods or reconnection caused the Plugin Host to exit; the Recovery Assistant now displays a summary of the Host’s first fatal error directly at the top of the error details; fixed HTTP 431 errors when accessing through a browser or local network after multiple restarts due to accumulated cookies. - UI interaction and Linux packaging: Fixed the inability to copy and paste in plugin views within applications such as Office, the inability to drag the window from the top of the automation page, the “Update Announcement” button not pointing to the current version by default, and the inability of the LiveShare reader client to load pages when certain plugins were enabled; added the desktop icon and Debian audio／graphics dependencies to the Linux packages.

Usage notes - Please exit the old application first and back up ~/.dsh (or use “Backup” in “Settings → Desktop Settings”), then verify your commonly used plugins and workflows after installation. - If you need to manage desktop Profile plugins through the in-app terminal, please start Desktop first to initialize that Profile. - When upgrading from 2.0.17-next or earlier, manual download and installation is recommended; in-app updates in older versions may be unable to complete the download. - When first used, the Office document skill will install the bundled runtime to ~/.dsh/dsh-runtimes/dsh-next-primary-runtime, requiring additional disk space. - By default, it shares ~/.dsh with the old stable version; Profiles do not isolate sessions, accounts, or credentials within the same directory. - You can switch the data directory in “Settings → Desktop Settings” or the Recovery Assistant, or isolate DSH data through the absolute path DSH_DESKTOP_NEXT_HOME (the in-app selection takes precedence over the environment variable), but this will not isolate AA’s default shared login and device-binding state.

Full changelog · Project website

DSH NEXT has replaced the original stable channel.