A path is not project identity
The same repository lives at different paths. dsh-alpha groups canonical Git identities and lets each Worker resolve its own safe location.
DSH orchestration plugin
One control plane for every coding agent.
Turn different machines, paths, and runtimes into one visible global inventory. A task leaves the same conversation with an explicit workspace, permission boundary, and recovery path.
7 runtimes
reverse WebSocket
event-driven
allowed roots
Rendered locally with open-source HyperFrames. Machine, workspace, and path details are redacted.
The missing layer
The hard part is not starting more agents.
It is getting a task to the right machine, repository, runtime, and permission boundary—and still knowing what happened after an approval or connection failure.
Capabilities stay visible
Machine status, Agent capabilities, load, and workspace affinity share one inventory for both automatic and manual routing.
Tasks must recover
Durable task IDs and an event stream mean an interrupted wait is not a cancellation, and missing events can be replayed after reconnect.
Control loop
Discover, choose, dispatch, approve, recover.
All five steps remain in one Alpha session. Keep automation flexible, or pin the Agent, model, effort, and permission mode for a critical turn.
01 / DISCOVERGlobal inventory
Combine live machines, workspaces, and Agents.
02 / SELECTConstrain scope
Choose a project or machine, or keep routing automatic.
03 / DISPATCHDurable task
Receive a task ID and stream progress events.
04 / APPROVEApproval handoff
Bring remote permission requests back to the session.
05 / RECOVERReconnect
Replay missing events and resume the same task.
Product tour
Keep the control plane in sight.
The control directory, global workspace selector, Worker routing, and model/permission controls all live inside DSH Web. Project-related details are redacted.
Launch note
Stop memorizing machines.
When product code, build toolchains, and test services live in different environments, the number of agents is not the main problem. Machine reachability, repository identity, capability differences, permissions, and recovery are what need a control plane.
dsh-alpha does not decide which Agent is always best. It keeps the reason for this turn's choice visible.
Upgrade a machine list into a global workspace
Each Worker discovers only the workspaces inside its allowed roots. The master groups locations by repository identity, then resolves the selected Worker's own path at execution time. On-demand clones remain inside the Worker's boundary.
Safety is not an appendix
The Gateway refuses to start without tokens. Paths must pass allowed-root checks. Health endpoints do not reveal identities or secrets. Worker doctor is read-only and never prints the token. Provider CLIs still keep their own authentication and permission models.
Start with one Worker
Configure a narrow allowed root on one remote machine, run Worker doctor, and verify discovery, capabilities, and result delivery. Add the next machine only after the first control loop is clear.
Quick start
Begin in DSH Web.
Install the plugin and Alpha preset, then open the control directory from the sidebar. Remote Workers can join one at a time.
Full documentation# Install the Web plugin dsh plugin --profile web add dsh-alpha # Install the Alpha preset node ~/.dsh/profiles/web/node_modules/\ dsh-alpha/scripts/install-preset.mjs # Start DSH Web dsh web