Multi-Machine Management

Cloud Only

Multi-machine management is available in the Cloud version only. The self-hosted version supports a single machine.

ADHDev Cloud lets one account keep track of multiple development machines from a single dashboard.

What It Gives You

• one dashboard for your laptop, desktop, work machine, or remote box
• machine-aware session visibility across IDE, CLI, and ACP workflows
• a machine detail page with launch controls, provider settings, logs, and session-host recovery
• cloud access outside your local network

This is one of the clearest differences between cloud and self-hosted. Cloud is the account-linked control plane. Self-hosted is one local dashboard per machine.

How It Works

Each machine runs its own ADHDev daemon, authenticated to the same cloud account:

npm install -g adhdev
adhdev setup
adhdev daemon

Once the machines are connected under the same account, they appear together in the dashboard.

Daemon Mesh Phase 0

Daemon Mesh Phase 0 is the first cloud-only daemon-to-daemon coordination path. It is intentionally narrower than a full P2P mesh:

• A source daemon can send a same-user daemon command through the cloud daemon WebSocket using daemon_mesh_command.
• DaemonConnectionDO and UserSessionDO validate that requester and target daemons belong to the same account before forwarding.
• The current built-in trigger is git_checkpoint_complete, configured through meshRules in the cloud daemon config.
• The target daemon executes the forwarded command through its normal internal command path and returns daemon_mesh_result.
• This is not a dashboard command fallback. Dashboard command/data traffic still uses P2P only in cloud mode.
• Direct daemon-to-daemon DataChannel mesh remains a later phase.

Burrows

The Burrows page is the machine-level overview. It is where you quickly see:

• which machines are online
• which machine a session belongs to
• connection and runtime status
• which machine you want to open in detail

Machine Detail

Opening a machine gives you a more operational view than the main dashboard:

• Workspace for current IDE, CLI, and ACP sessions
• Hosted Runtimes for hosted CLI runtime diagnostics and recovery
• Providers for machine/provider settings
• System for machine health
• Logs for runtime and daemon logs

This is the page you use when the high-level dashboard tells you something is wrong but you need machine-specific context.

Typical Uses

Multi-machine cloud setups are especially useful when you:

• keep one machine on background agent work
• separate personal and work devices
• want mobile approvals for sessions running somewhere else
• need to recover a CLI runtime on a machine you are not physically using

Plan Limits

Plan	Max Machines
Free	1
Pro	3
Team	10
Enterprise	Unlimited

When you hit your machine limit, additional machine registrations are rejected until you remove one or upgrade.

Self-hosted Difference

Self-hosted does not merge multiple machines into one hosted dashboard.

Use self-hosted when you want a local-only dashboard for one machine. Use cloud when you want account-linked machine visibility across devices.

Naming Machines

Friendly machine names matter once you have more than one box connected.

Machine nicknames appear throughout the dashboard and help disambiguate where a session is actually running.

Next Steps

• Dashboard →
• Mobile →
• Collaboration →
• Plan & Limits →