Troubleshooting
A machine is missing or offline
Section titled “A machine is missing or offline”- Confirm that Dash Desktop is running on the target computer and the computer is awake and connected to the internet.
- Check that both clients are signed in to the same account.
- Open account settings and refresh the connection status.
- Check whether the Desktop installation’s access was revoked under Signed-in Devices.
Remembered machines can appear while offline. Their files and live tools require a connection to the host. On Dash Free, networks that prevent direct peer-to-peer connections can prevent remote access; Dash Pro includes Relay traffic fallback.
A remote terminal or file is unavailable
Section titled “A remote terminal or file is unavailable”Check the machine shown for that view. The folder and terminal belong to that machine, even when another computer has the same path. Confirm that the host is online and that the folder still exists and is accessible there.
Reconnect before repeating a command: work on the host may have continued while your viewing connection was interrupted. See Remote machines and terminals.
A model is missing or unavailable
Section titled “A model is missing or unavailable”Open Models for the machine that should host the model and use Refresh. Check that the download has finished and the installed files passed verification. Reinstall a model marked as having missing or changed files.
The model picker lists installations by machine. Installing a model on one computer does not install it on every signed-in computer. An agent needs a reachable machine hosting its selected model.
An agent is waiting
Section titled “An agent is waiting”Look for Approval needed in the conversation. Review the proposed action and choose Approve once or Deny. Also check the host and model machine’s connection status.
Closing a view does not stop an agent run. Reopen the conversation and use Stop run if that is what you intend. To change the session’s file or command permission policy, start a new conversation.
An MCP client cannot connect
Section titled “An MCP client cannot connect”For Local MCP, keep Dash Desktop running on the same machine as the client and copy the current URL from MCP clients. If the local gateway’s port is unavailable, change the port in settings and update the client configuration. Complete the sign-in and approval flow; possessing the URL alone is not access.
For Relay MCP, check that the account has Dash Pro, the target machine is online, and that the integration has been allowed on that machine. Review its machine, project, and action permissions. See Connect an assistant with MCP.
Account data stays locked after a password reset
Section titled “Account data stays locked after a password reset”An email password reset restores login access. It does not by itself unlock encrypted account data. In account security, use the new login password and your saved recovery key to recover the data. See Account, sync, and privacy.
A Desktop update failed
Section titled “A Desktop update failed”Use Retry Update in the top bar. If the update is downloaded, save your work and use Restart to Update. You can also install the appropriate build from the Dash download page.
Get help
Section titled “Get help”Contact [email protected] with your operating system, Dash version, the feature you were using, and the error text. For remote problems, include which client you were viewing from and which machine was performing the work. Remove passwords, recovery keys, tokens, and private content from screenshots or logs before sending them.