DeepSeek Harness for desktop
dsh-helper
Also known as dsh helper, dshhelper, DSHHelper, DSH Helper, or DeepSeek Harness Helper
One desktop, unlimited instances
dsh-helper keeps support, engineering, and testing from sharing one dsh. Each instance is a complete, isolated Harness — in one workspace; a tuned environment is the product, and export is delivery.
Windows · macOS · Linux · GitHub Releases
- Support
- Code
- Tests
- Orchestrate
- Build
- Docs
- Test
- Review
- Frontend
- Backend
- Tests
- Package
Isolated plugins · one workspace · export is delivery
01 Isolate
One instance cannot host multiple workloads
Unrelated plugins in one preset make the model call the wrong tools. Isolate the workloads first — then collaborate, then deliver.
The problem
Customer messages, code, and tests share one DSH_HOME. The tool list grows until the model misroutes. Three capability sets cannot coexist in one preset.
Agent presets do not resolve this: only one mounts per session, and switching after a turn is locked.
Per DeepSeek Harness: Agent Presets and Personas
The approach
In dsh-helper, each instance is a complete, isolated dsh — own process, port, and DSH_HOME. Create as many as you need. Plugin environments never conflict. Isolate, then run in parallel, then package.
02 Collaborate
Specialist instances, one workspace
Plugin sets stay isolated. Project files stay in view. You orchestrate from the panes — a configured instance is ready to export.
Each instance is a specialist: support, engineering, testing. Plugins are its toolchain, so they must be isolated.
Spreading them across three machines is three separate environments — multiplied hardware, files copied back and forth, no shared state. Place them on one computer, against the same project folder. Not three unrelated windows — one workspace advancing one release.
03 Deliver
The environment is the product. Export is delivery.
You don't ship a README. You ship a tuned environment — plugins, preset, and working folder included. Export is delivery.
After configuring support, engineering, and testing, delivery often fails not on “can they use it”, but because every handoff feels like rebuilding the project.
- Cannot reproduce Days later even you cannot confirm which plugins and which preset constitute the product.
- Cannot hand off A README never guarantees a clean install; shipping the folder invites redistribution.
- Cannot scale The next customer still requires the same remote setup. Delivery time dwarfs the time spent configuring.
A .dshpack encapsulates that tuned environment as a file. They import and run. Bind a machine code or password; forbid re-export. Configure several instances, export several packs.
Get started
Install dsh-helper. Create instances.
Windows, macOS, and Linux. The wizard pulls the runtime. Then you split panes.
- Install Download the build for your platform from Releases.
- Initialize Choose a data folder, pull the runtime, create the first instance.
- Split Create more instances. Drag tabs to the edges. Run them in one workspace.
Free download · not code-signed yet · runtime downloads on first run
Next
From isolation to delivery,
on one desktop.
Isolate workloads in dsh-helper. Collaborate in one workspace. Export a tuned environment as a .dshpack.