Skip to content

dsh-launcher v0.4.0

Latest

Choose a tag to compare

@Wanbinyu Wanbinyu released this 26 Aug 07:24
· 1 commit to main since this release

dsh-launcher v0.4.0

一键安装 DeepSeek Harness

  • 首次启动自动检查 Node.js 22.19.0+、npm、winget 和现有 Harness。
  • 没有 Node.js 时,经用户确认后通过 Windows Package Manager 安装 Node.js LTS。
  • 从 npm 安装并校验官方 @deepseek-ai/dsh 包,不要求访问 GitHub。
  • 内置受管 pnpm,降低大量 Harness 子包首次解析时的耗时和内存;构建脚本采用明确白名单。
  • 使用当前用户独立的受管目录,不覆盖源码目录、全局安装或现有 Web profile。
  • 新增安装进度、实时输出、取消和可操作的失败信息。
  • 托盘新增 Harness 安装、更新、修复、打开目录和卸载入口。
  • 卸载受管 Harness 不删除插件、会话、工作区或 %USERPROFILE%\.dsh 数据。

获取启动器安装包后,首次安装 Harness 仍需要访问 npm registry。Node.js 安装可能触发正常的 Windows 权限确认。


One-click DeepSeek Harness setup

  • Detects Node.js 22.19.0+, npm, winget, and existing Harness installations on first launch.
  • Installs Node.js LTS through Windows Package Manager after explicit consent when needed.
  • Installs and validates the official @deepseek-ai/dsh package from npm without requiring GitHub access.
  • Bootstraps a managed pnpm to reduce first-install resolution time and memory across the large Harness package graph, with an explicit build-script allowlist.
  • Uses an isolated per-user managed directory and does not overwrite source checkouts, global installations, or existing Web profiles.
  • Adds live setup progress, command output, cancellation, and actionable failure details.
  • Adds tray actions to install, update, repair, open, or remove the managed Harness copy.
  • Managed removal preserves plugins, sessions, workspaces, and %USERPROFILE%\.dsh data.

After obtaining the launcher installer, npm registry access is still required for the first Harness installation. A normal Windows permission prompt may appear while installing Node.js.