Your remote development workspace
Keep your repositories, development tools and coding agents on a Linux machine you control. Connect from your laptop, open the right worktree, and view your app through a private tunnel.
Choose your starting point
- Quickstart: move from a local repository to an editor on your host.
- Install the client: macOS and Linux, without sudo.
- Prepare a host: prerequisites, SSH trust and optional enrollment.
- Troubleshooting: reconnect, repair inventory and diagnose setup failures.
What lives where
| Location | Responsibility |
|---|---|
| Your laptop | CLI, editor, SSH keys and local tunnel endpoints |
| Your Linux host | Repositories, running agents, vendor sign-ins and dev servers |
| Optional hosted control plane | Identity, authorization, observed machine/workspace/session metadata |
| Optional relay | Transport for encrypted SSH; not an agent conversation protocol |
Two ways to connect
Direct SSH works without hosted enrollment. Add an existing trusted SSH alias, prepare your repo, and open it. Use a VPN alias when your host is reachable through your own network.
Hosted enrollment adds machine observations and an optional outbound relay for machines without publicly reachable SSH. An independently hosted relay is also supported. Compare connection methods.
Know the boundaries
A persistent filesystem survives disconnection and normal host reboots when its disk survives. Running tmux sessions survive a laptop disconnect, but do not survive a host reboot. Worktrees under one Unix user are not security sandboxes.
Devboxes are for development and temporary services, not production hosting. You own the host, its operating system, backups and vendor subscriptions.