Remote machines and terminals
Connect a machine
Section titled “Connect a machine”- Install and open Dash Desktop on the computer you want to reach.
- Sign in to your Dash Cloud account on that computer.
- Sign in to the same account in Dash Desktop on another computer, or in Dash Web.
- Find the target machine in the sidebar and check that it is online.
- Expand its projects and open the file or tool you want to use.
Keep the target computer awake, connected to the internet, and running Dash Desktop. A machine can be remembered in your account while unavailable for live work.
Where work happens
Section titled “Where work happens”Remote terminals and commands run on the target machine, using its operating system account, shell, installed tools, and files. For example, a terminal opened under a Linux machine uses that Linux environment even when you view it from a Mac or phone.
Right-click a folder and choose New Terminal to open a shell in that folder on its machine. Check the selected machine and working directory before running a command. Losing the viewing connection does not itself guarantee that work running on the host has stopped.
Agent conversations and model installations also belong to their host machine. Agents and models explains how the model host can differ from the machine where tools perform work.
Direct connections and Relay
Section titled “Direct connections and Relay”Dash Free uses direct peer-to-peer connections between your clients. Dash Pro adds Relay traffic fallback when a direct connection cannot be established, as well as Relay MCP.
Supported ordinary traffic between Dash clients is encrypted between the participating clients, including when it travels through Dash Relay. Connection services still handle routing information and traffic metadata. Relay MCP has a separate privacy boundary: its hosted endpoint reads the authorized tool inputs and results.
Some networks prevent direct connections. If a machine is signed in but cannot be reached, check its status and network before changing the project or restarting your work. More checks are in Troubleshooting.
Desktop browser views
Section titled “Desktop browser views”Embedded browser tabs run on the Desktop machine that owns them. Remote browser viewing is not currently available; open those views on their host computer. This limitation does not prevent you from using Dash Web for supported remote files, terminals, and agent views.
Remove a device’s account access
Section titled “Remove a device’s account access”In account settings, find Signed-in Devices and choose Revoke access for the Desktop installation. Confirm with your password or recovery key. Revocation prevents future account access; it cannot erase data or keys the device already received.