DSHBox

DSH Box

English · 简体中文

Managed DeepSeek Harness desktop runtime — run, isolate, and extend multiple DeepSeek Harness environments on your own machine, no browser tab required.

DSH Box is a lightweight desktop shell built with Tauri 2 that installs, launches, and manages independent DSH Containers — each with its own DSH version, profile, plugins, skills, workspace, and logs — and renders them in an embedded WebView.

Highlights Isolated containers — one DSH version, profile, workspace and host process each. Optional VM runtime (experimental) — a container may declare runtime: "vm" / "vm: "; host mode stays the default. Windows uses one WSL2 distro per container, Linux a libkrun microVM. See the runtime design note. Embedded WebView — the DSH UI opens in a native window; no ports, no URLs to paste. Ready in seconds — a pulled Harness version arrives with its client artifacts built; run is a copy (~10s). Plugin dependency graph — what loads, in what order, why: depth bands, halves apart, fold a depth away. Resources: extract, inject, edit — conversations, keys and plugin state as named copies; any YAML block editable by key path. An agent surface — dshbox apply -f configures resources from one document; every verb answers --json. An agent inside a container — the dsh-box-sandbox plugin gives an agent running inside a container typed box_* tools, so it drives the box that contains it with no shell and nothing to install. Zero-dependency install — bundled Node, npm, pnpm and Git (Windows), in a clean room. Version manager — install any Harness tag and pin a version per container

Download the installer for your platform from the Releases page of this repository: Grab the latest version from the Releases page — artifact names follow the - - convention. Every tagged release carries all three platforms, built by the release workflow.

No runtime prerequisites on Windows — the bundled Node/npm/pnpm/Git runtime travels inside the installer. Linux needs a system Git (apt install git or your distro equivalent); its configuration is isolated per-runtime-directory, so your host ~/.gitconfig is never read by DSH Box builds. Quick start

1. Launch DSH Box and pick a writable *runtime directory* when prompted (all DSH data lives there). 2. Open Resources → DSH Versions → Load versions, then install the DSH tag you want. 3. Open Resources → Templates, then pull an official DSH template or build a reusable template from a Boxfile. 4. Open Container → create a Container from that template (name and profile). 5. The first create prepares the Container in its final directory (offline dependency install, local plugins, fron