Remote Development
Run Emdash work on remote machines and managed workspaces
Remote development in Emdash lets you keep the UI on your local machine while project work runs somewhere else. That can be a persistent server you connect to over SSH, or an ephemeral workspace provisioned by your own infrastructure scripts.
Remote Projects vs Remote Tasks
Use Remote Projects when a project should always run on one persistent remote server. Use Remote Tasks when selected tasks should get their own isolated workspaces, so agents do not share the same machine and you can scale by provisioning more workspaces.
| Remote Projects | Remote Tasks | |
|---|---|---|
| Best for | Projects that should always run on a remote server | Tasks that need their own isolated environment |
| Where work runs | Every task runs on the project's remote machine | Selected tasks run in provisioned remote workspaces |
| Lifecycle | Long-lived server you manage | Workspace created and destroyed per task |
| Setup | Saved SSH connection in Emdash | Provision and terminate scripts per project |
Use these pages based on what you are setting up:
- Remote Projects: connect Emdash to a repository on a persistent remote machine.
- Remote Tasks: provision per-task remote workspaces with your own scripts.
- SSH Connections: manage reusable SSH connections for remote projects.
Last updated on June 30, 2026