devbox open-ide is the common path for most editors. It configures local SSH access, then launches the editor already connected to your Devbox, so there is nothing to set up by hand.
VS Code
VS Code opens on your machine and connects to the Devbox over SSH, so your files, terminal, and extensions all run remotely.- CLI
- Dashboard
- Configure local SSH access to your Devbox
- Ensure the Remote - SSH extension is installed (see the VS Code Remote-SSH documentation for more details)
- Open a new window connected to your Devbox
Cursor
Cursor opens as its own desktop app, connected to your Devbox over SSH.- CLI
- Dashboard
Pass
--flavor cursor to launch Cursor instead of VS Code:JetBrains
JetBrains IDEs support remote development through JetBrains Gateway or the built-in remote development features in IDEs like IntelliJ IDEA, GoLand, PyCharm, and WebStorm. See the JetBrains remote development documentation for more details.- Configure SSH access. This writes the SSH key and proxy config so Gateway can connect without manual setup:
- Open JetBrains Gateway and select SSH Connection
- Create a new connection with the host
my-devbox.devbox.namespaceand usernamedevbox - Select the IDE and project directory on the remote host
Zed
Open your Devbox in Zed:Other editors
--flavor also accepts vscode-insiders, codium, positron, and windsurf. Each launches that editor’s own desktop app, connected over the same SSH access:
devbox open-ide for the full list of accepted values.
Connect manually
To use an editor thatopen-ide does not support, run devbox configure-ssh first (see Configure SSH), then connect from your IDE using the SSH host. The dashboard’s Copy SSH command option gives you the same connection details. You may need to specify a working directory. Use /workspaces/{repo-name} if you created your Devbox with --checkout.
Next Steps
Remote Development
SSH access and SSH config for a Devbox.
Sessions
Persistent terminal sessions that survive disconnections.
devbox open-ide
Every flag accepted by
open-ide.