How dsh-web-all works
DeepSeek Harness loads dsh-web-all through the official profile mechanism and attaches its modules to dsh web without modifying the official source. The aggregate package includes the family’s feature plugins rather than replacing the host’s core conversation and tool-calling functions. DeepSeek Harness stores shared application data under ~/.dsh; the official desktop client and dsh web use the same directory.
Configuring dsh-web-all
The README documents configuration through the Web UI rather than a standalone configuration file. Relevant settings include:
- Task details accept a Cron expression for background scheduling.
- Task execution can enable session reuse.
- Goal tasks can enable task acceptance, with a selectable model and reasoning level under
设置 → Web 插件 → 任务看板 → 任务验收.
- The task board can enable power management to prevent system sleep while allowing the display to turn off.
- Model capability settings declare image input support and reasoning levels for individual models.
Task-acceptance configuration is fixed when an execution starts. A failed first assessment sends feedback to the agent for repair; a second failure marks the execution as failed. Each assessment consumes the selected judge model’s quota.
dsh-web-all features
The package provides a task board with five states: planned, pending, running, completed and failed. It can start real DeepSeek Harness agent sessions, link cards to their sessions, and retain results after scheduled execution. Other modules provide mobile QR pairing, WebSocket streaming, SSH terminal access, SFTP transfer, port-forwarding tunnels, cluster commands, Git graphs, automatic Git Worktree directories, session search and archival, token usage and cost views, provider balance queries, model capability editing, skins and desktop pets.
Requirements and limits
The README shows compatibility with DeepSeek Harness >=0.2.0-rc.2. The power-management option supports Windows, macOS and Linux systems with systemd-logind. The official desktop client uses the desktop profile and restricts external CLI changes to that profile, so desktop installation is managed inside the client. The README does not document additional environment variables or standalone commands added by the aggregate package.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub