What It Is

DSH is the official open-source Agent runtime from DeepSeek: the model handles "thinking," and Harness handles "doing." It writes sessions, credentials, settings, user presets, and Profiles all into a single DSH_HOME directory.

Installing one DSH is simple, but to use it well, you quickly find you lack a "multi-open" capability:

• Want to run two tasks at the same time without mixing up sessions and API Keys;
• Want to experiment with different Provider / model configurations without touching your everyday environment;
• Want several Agents each owning a piece of the work, with results merged at the end.

DSH Launcher turns these into everyday desktop operations. It is built on Tauri 2, and the launcher and each instance are separate processes: every instance has its own window, taskbar entry, port, Profile, and a mutually disconnected DSH_HOME. The isolation here is not a surface-level "separate folders" trick — it is a hard runtime boundary.

Why It's Different

🔒 Every instance is a "fresh DSH"

Creating a brand-new DSH_HOME is essentially a two-step process: pick a brand-new empty directory, then point the DSH_HOME environment variable at it when launching the DSH child process.

# 1. 选一个全新的空目录
$fresh = "D:\dsh-instances\tauri"
New-Item -ItemType Directory -Path $fresh -Force

# 2. 启动时只把这个环境变量传给子进程，不污染系统环境变量
$env:DSH_HOME = $fresh
dsh web   # 自动初始化官方 web profile

DSH writes everything into DSH_HOME:

独立 DSH_HOME
├── .credentials.yaml   API Key
├── settings.yaml       Provider / 模型设置
├── sessions/           会话历史
├── .agent-presets/     用户 Agent 预设
├── storages/           应用存储
└── profiles/           Profile 组成与补丁

The isolation boundary is DSH_HOME, not Profile. As long as you don't copy an old directory, a new instance inherits no old data: sessions, Keys, presets, caches — all start from zero. Dev, experiment, demo environments: have as many as you want, each independent, never "crossing flavors."

🤝 Multi-instance collaboration: your very own Agent team

Isolation keeps them separate; collaboration makes them work together.

In the collaboration panel, orchestrate multiple instances like a flowchart: each node is a running DSH instance handling a coarse-grained task; nodes connect via dependency lines — parent-child run in order, siblings serially or in parallel; each node passes its outputs (text, file paths) downstream.

Under the hood it's a lightweight RPC: the main instance dispatches, polls, and cancels tasks on running instances through a loopback HTTP interface (POST /api/<method>). The host is restricted to 127.0.0.1, the trust boundary is clear, and no extra tokens are required.

Split one big task across several Agents, each with its own strengths, each progressing inside its own DSH_HOME, with the main instance aggregating the results at the end. That's a reusable multi-Agent pipeline.

UI Preview

_{新建实例界面 ｜ 启动实例界面}

_{多实例协作画布，创作你的工作流 ｜ 创建好的工作流下次直接复用}

_{插件包下载 ｜ 插件包市场：在插件社区下建立二级社区插件包，下载和分享插件组合}

_{导出用户配置界面 ｜ 全局运行日志一键复制，轻松定位插件导致的实例报错}

_{双隔离机制，几乎兼容 DSH 的各种更新 ｜ 精简配置，出现错误时利用多实例机制灵活修复启动逻辑}

_{个性化调色盘启动器}

Feature Overview

Capability	Description
Multi-instance lifecycle	Create, start, stop, restart, remove; ports are auto-detected, and only actually listening ports are shown
Full isolation	Each instance has its own DSH_HOME / window / port / Profile; instances sharing the same Home are not allowed to run in parallel
Collaborative orchestration	Canvas-based instance dependency orchestration, serial / parallel execution, outputs passed along the chain
Plugin ecosystem	Community plugin catalog + plugin package marketplace, supporting npm, GitHub, and trusted HTTP(S) packages
Background installation	Plugins installed one by one, real progress, cancel anytime and terminate the entire child process tree
Runtime management	DSH runtime downloads, checksum verification, transactional replacement; updates never lose instance data
Export & backup	Selective Profile export, full Home backup; sensitive data stays on the local machine only
Privacy boundary	Keys, sessions, settings, and logs are all stored locally; nothing goes into the repo or gets uploaded

Architecture

┌──────────────────────────────────────────────────────────────┐
│                 DSH Launcher 进程（Tauri 2）                  │
│        实例注册表 · 生命周期 · 插件 · Runtime · 托盘 · IPC      │
└───────────────┬───────────────────────────────┬──────────────┘
                │ 进程隔离：窗口 / 端口 / 变量    │ RPC：下发 / 轮询 / 取消
   ┌────────────▼─────────┐   ┌─────────────────▼──────────────┐
   │      实例宿主 1       │   │         实例宿主 2              │
   │  独立窗口 · 独立端口  │   │  独立窗口 · 独立端口            │
   │  独立任务栏入口       │   │  独立任务栏入口                 │
   └────────────┬─────────┘   └─────────────────┬──────────────┘
                ▼                               ▼
        DSH 原生 Web                     DSH 原生 Web
        DSH_HOME = A                      DSH_HOME = B

The launcher only "manages" — it never touches the DSH core: no rewriting of DSH's Web routes, sessions, API Keys, Agent presets, or plugin logic; it only maintains the external runtime contract. So DSH updates usually don't require the wrapper to change in sync.

Quick Start

• Installer: download the Windows installer, then launch it from the Start menu or the desktop shortcut after installation.
• Portable (Windows x64): download the Windows portable edition directly — double-click to run, no installation needed.

No manual Node.js or DSH install needed. On first launch, the launcher auto-detects and downloads missing runtimes online; existing compatible ones are reused first.

The Release ships Windows, macOS, and Linux builds. The primary desktop acceptance platform is currently Windows; a successful macOS / Linux build does not mean all real-device feature verification has been completed.

For first-time setup, plugins, collaboration, backup, and troubleshooting, see the User Guide.

Docs

• Architecture & Data Flow · Tauri IPC Contracts
• Visual Guidelines · Development Notes · Release Checklist
• AI Development Constraints · Current TODOs and Known Limitations

Building from Source

pnpm install
pnpm tauri dev                 # 开发调试
pnpm tauri build --bundles nsis   # 产出 Windows 安装包

Installers are output to src-tauri/target/release/bundle/nsis/. The Windows portable exe (double-click to run, no installation needed) is available from the v0.0.14 Release. See docs/DEVELOPMENT.md for development details.

Privacy Boundary

API Keys, tokens, passwords, sessions, DSH Home, Profiles, logs, caches, and local settings never enter the repository or release packages. Build directories such as dist, src-tauri/target, and node_modules are already ignored. The source repository only contains project code, build configuration, documentation, public static assets, and the distributable packages.

License

MIT + Supplementary Terms (non-commercial use)

---

If DSH Launcher has been useful to you, a Star is very much appreciated — or share it with friends who are also using DSH.