DSH Desktop: Composable Agent Harness

Overview

DSH Desktop adds a native entry point, lifecycle control, packaged runtime, and recovery around the pinned DeepSeek Harness without replacing its agents, models, tools, sessions, or Web client. The series follows launch, generation-scoped profile changes, public plugin contracts, package execution, runtime closure, renderer and update boundaries, and the residual power of local plugins and chosen providers. Its central lesson is conditional: composability depends on explicit ownership, restart and health gates, and evidence matched to each claim—not on hiding complexity or treating local, sandboxed, recovered, or packaged as synonymous with trusted.

Learning outcomes

DSH Desktop is an operational adapter around DeepSeek Harness, not a replacement for its agent runtime or Web client.
A profile or presentation change crosses a generation boundary and requires restart, trading interruption for clearer ownership.
Public services expose profile, package, and geometry capabilities without making private Electron state a plugin API.
Loopback, renderer controls, health gates, and update consent limit specific paths; they do not sandbox plugins or authenticate LAN access.

Keywords

DSH DesktopDeepSeek HarnessComposabilityPluginsProfilesElectronLifecycleRuntimeSecurityRecovery

Chapters

DSH Desktop: Why a Native Shell?

Native lifecycle control without forking Harness

8 min · Native lifecycle control without forking Harness

8 min

DSH Desktop: From Launch to Web Surface

How profile, Host, carrier, and renderer reach health

11 min · How profile, Host, carrier, and renderer reach health

11 min

DSH Desktop: Profile Changes and Recovery

Why restart fencing protects composition identity

10 min · Why restart fencing protects composition identity

10 min

DSH Desktop: Public Plugin Contracts

What services expose—and private Electron keeps closed

8 min · What services expose—and private Electron keeps closed

8 min

DSH Desktop: Packaged Tools and Runtime Closure

What execution control and release checks can prove

12 min · What execution control and release checks can prove

12 min

DSH Desktop: Security, Recovery, and Updates

Where local access stops short of authentication

12 min · Where local access stops short of authentication

12 min

DSH Desktop: Composability as Product Discipline

What explicit boundaries make sustainable—and what they cannot guarantee

13 min · What explicit boundaries make sustainable—and what they cannot guarantee

13 min

Preview every chapter · Unlock full text, audio, and video from chapter 4

Plans

Ch.1-3 FreeCh.4-7 Premium

FAQ

What does DSH Desktop add to DeepSeek Harness?

DSH Desktop adds a native entry point, local process and window lifecycle, profile management, packaged tools, and recovery around the existing Harness. DeepSeek Harness remains authoritative for agents, models, tools, sessions, and Web behavior.

Why does DSH Desktop restart when a profile or mode changes?

DSH Desktop restarts because a profile or mode changes the composition’s identity and ownership. Ending one generation before starting the next prevents stale services, renderers, subprocesses, and layout owners from being mixed, at the cost of interruption.

Are DSH Desktop plugins sandboxed?

No, DSH Desktop plugins are not security-sandboxed merely because they use declared services or the renderer is sandboxed. Installed plugins and dependencies run locally with their processes’ permissions, while public contracts mainly reduce hidden coupling.

How reliable is DSH Desktop’s last-known-good recovery?

It can restore declarative profile and Harness-home configuration captured after a healthy startup, but it is not a full backup or universal rollback. Credentials, sessions, storage, caches, generated dependencies, provider failures, and some plugin defects remain outside that boundary.