Concepts
Concept hierarchy
server → node (one DSH agent process + its own DSH_HOME) → workspace (identity + directory + preset + sandbox) → session- Node = one DSH agent process with its own
DSH_HOME. Sessions, settings and attachments of one node are invisible to other nodes. - Workspace = the directory a node works on. Files are the source of truth: one git repository per workspace, one commit per run (audit trail).
- Session = a conversation; serial within a session, parallel across sessions.
Roles
| Role | What it does |
|---|---|
| manager | The control plane: authentication, chat relay, brain dispatch, node and machine management, skill inventory, cost accounting, backup and restore |
| brain | Manager-level chief controller: cross-domain planning, work orders, fleet queries. Read-only on workspaces — execution is always delegated |
| workspace agent | The agent that does the work in a workspace: reads files, writes files, leaves a git trail |
Say what you want in a brain session, e.g. "Rewrite the product workspace README in Chinese and commit it." The brain plans, dispatches to the right node, and relays the result. Delegation frames appear in the conversation and link to the dispatched session.
Machines and the fleet
A machine is a server that joined through the node agent, so the manager can start, stop and read logs from that host. One join command per server (token valid 15 minutes, one-time). The agent is a fixed command set (not a generic shell), dials out with zero inbound ports, and nodes keep running when the manager is down — the agent reconnects and reconciles on recovery.