The Harness service listens on the loopback address 127.0.0.1, and the desktop app embeds
that local Web interface. Sessions and profiles stay on your computer, but model providers
and installed plugins may have their own network behavior.
Data boundaries
Network use
The application needs network access to download Node.js, pnpm, supporting tools, or the
core; check for desktop and core updates; install plugins from npm or GitHub; call a model
provider; or run a plugin or tool that accesses a remote service.
Harness executes tools and code. An application profile is not a sandbox. Use operating
system isolation, least-privilege credentials, reviewed plugins, and trusted workspaces
according to the risk.
Back up or reset
Back up ~/.dsh before moving a profile or attempting destructive repair. Remove API keys,
user names, local paths, prompts, and repository content before publishing logs. Development
builds use separate ~/.dsh.dev, .store.dev.dat, and logs/dsh-web.dev.log data. 