A machine that stays yours.
Your files, dependencies and development environment live on a Linux host you control. A home server, a spare box or your own VPS.
PERSISTENT BY DESIGNYOUR MACHINE. YOUR RULES.
Give your code and coding agents a place to stay. Turn your Linux machine into a persistent dev environment, ready from wherever you work.
Bring your own host. Keep your tools. Pick up where you left off.
START ON YOUR LAPTOP
Install the client, then connect your own Linux host.
curl -fsSL https://devbox.508.dev/install.sh | shmacOS or Linux · Node.js 24+ required · No sudo
Install guide · Prepare your host
FAMILIAR TOOLS. A BETTER PLACE TO RUN THEM.
LESS SETUP. MORE MOMENTUM.
Stop rebuilding your context every time you change screens. Keep your repositories, tools and running sessions together.
Your files, dependencies and development environment live on a Linux host you control. A home server, a spare box or your own VPS.
PERSISTENT BY DESIGNFind the right repo, branch or tool-created worktree. Open it in your preferred editor or agent, and see observed Paseo sessions in your dashboard.
LESS “WHICH FOLDER WAS THAT?”Run your dev server on the box and view it locally through a private SSH tunnel. Keep working in the browser you already use.
DEVELOP REMOTELY. SEE IT LOCALLY.FROM REPO TO READY
Bring a Linux host with SSH access. Authenticate your coding tools on the host, then make yourself at home.
Add a trusted SSH connection. Direct, VPN or a configured relay — multiple routes can reach the same box.
devbox connection add home --ssh my-boxStart in your local repo and prepare a remote workspace. Your laptop’s SSH keys and provider credentials stay put.
devbox setup --computer homeLaunch your editor or agent in the right workspace. Host-owned terminal sessions keep running when you disconnect.
devbox open --computer home --with codeYOUR HOST. YOUR BOUNDARIES.
Use direct SSH when you can, a hosted or self-hosted relay when you need it. SSH stays encrypted through the relay. Vendor sign-ins stay in your private host account, and prompts and transcripts stay out of the heartbeat inventory.
Make room for your next ideaYour development environment
Checking sign-in…
Sign-in opens a separate tab. Return here afterward to keep your selected computer and local CLI connection.
Sign inOnly enter a code displayed by a CLI sign-in you started yourself. Review its scopes and explicitly select the computers it may access.
Session command center
Watch existing Paseo sessions and attach to their workspace terminals. Explicit pairing grants full machine control. Nothing from this view is stored in the hosted control plane.
The activity below belongs to this exact session. Workspace launch buttons below start or configure a separate vendor connection; they do not resume this conversation. Use Open Paseo to continue the existing session.
Select a session to watch its activity.
Select a session to find its workspace terminals.
Find the exact checkout or worktree. Run devbox browser on your laptop to launch Claude on this workspace. For ChatGPT desktop, add --ssh-host <alias> for this computer; the app connects to that host and lets you select the folder.
| Repository | Branch | Remote folder | Open with |
|---|
devbox workspace enter
This periodically observed inventory is separate from the live connection above. Open Paseo to continue agents and manage terminals. Prompts and transcripts are never sent to the control plane.
| Session | Agent | Workspace | State |
|---|
Open a discovered HTTP service in an expiring browser preview when your host is configured for it. Access is private to you; browser traffic passes through the preview gateway. You can also run devbox preview on your laptop for a private SSH tunnel.
| Workspace | Service | Source | Preview |
|---|
devbox previewRun devbox doctor on your laptop for connection and workspace diagnostics. Your existing SSH and on-host cws helper remain available.