Editors and coding agents
Devbox gets you to the right machine and worktree. Your editor or vendor tool owns its interaction, authentication, permissions and conversation history.
VS Code and Cursor
devbox open --computer home --with code
devbox open --computer home --with cursorInstall the editor and its Remote SSH support locally. The CLI creates a narrow SSH include for this connection, preserving your existing configuration and pinning the verified host key. Subsequent editor SSH connections use the same route selection.
Claude, Codex and a shell
Install and authenticate vendor CLIs on the host first:
devbox open --computer home --with claude
devbox open --computer home --with codex
devbox open --computer home --with shellThese use stable host tmux sessions. Ctrl+B, then D detaches. Reopening the same launch can reattach. A laptop disconnect does not kill the process; a host reboot does.
Native permission prompts remain interactive. Opening another tool on the same worktree does not migrate a conversation into that tool.
Paseo
devbox open --computer home --with paseoPaseo owns agent interaction and existing session continuation. Its separate relay is enabled only through explicit pairing. A pairing offer grants machine control; review it before approving.
T3
devbox open --computer home --with t3The current path provides SSH setup instructions and the exact remote folder. It does not claim a supported exact-worktree deep link into T3. Supported T3 worktrees/projects can still appear in owner-local discovery.
Browser handoff
devbox browserThe laptop launcher opens the hosted dashboard and retains its local bearer only in tab memory. It supports Claude Remote Control, native Claude Desktop SSH links and Codex desktop SSH connection setup, as detailed below. It is separate from continuing an existing Paseo conversation.
The host-side tmux process can survive the launcher disconnecting. Browser-to-laptop launch authorization itself expires; restart devbox browser to establish a new one.
Native desktop apps: choose the action explicitly
devbox open --computer home --with claude-desktop
devbox open --computer home --with codex-desktop
# A custom destination works with either:
devbox open --computer home --remote-dir '~/src/payments' --with claude-desktop| Action | Result | Existing conversation? |
|---|---|---|
--with claude / --with codex | Remote terminal CLI in its stable tmux session | Reattaches that tmux process; the vendor owns conversation selection. |
--with claude-desktop | Native SSH link with the verified host alias and exact remote folder | A **new** Desktop session, after confirmation; no terminal conversation is migrated. |
--with codex-desktop | Native SSH connection setup with the verified host alias | Connect and **select the printed remote folder manually**. No automatic remote-folder/new-thread link is claimed. |
| Dashboard **Claude web / Remote Control** | Host Claude Remote Control session and vendor HTTPS page | Reattaches the platform's stable host session when available. |
| Dashboard **Claude Desktop · new session** | Host-and-folder SSH link | New session after vendor confirmation. |
| Dashboard **Codex desktop · SSH setup** | Connection setup link plus exact folder | Manual connection/folder selection. |
| Existing Paseo session link | Paseo's supported continuation | Paseo owns that session and its conversation. |
The CLI generates a narrow SSH config include and verified host-key pin for the chosen computer. Desktop SSH uses that alias and the same direct/VPN/relay route selection. The CLI must remain installed and its configured route credentials must remain available for the alias's ProxyCommand. No SSH private keys or vendor tokens are placed in links.
Claude's documented SSH links require Desktop **2.110.0 or later**; older builds may ignore the host/folder parameters. Use a current macOS/Linux Desktop with its OpenSSH backend and test the printed alias with ssh <alias> first. The vendor asks for confirmation and may require host login/trust. Devbox does not report a desktop connection as ready merely because it produced a link. GUI acceptance with your installed vendor build is still required.
Codex's documented link opens connection settings; it does not automatically connect or select a remote folder. Local codex://new?path=… links must not be used for remote paths. Until the vendor exposes a documented remote-folder action, use the setup link and exact folder, or --with codex for a direct terminal launch. T3 also remains an explicit SSH setup flow.
Dashboard actions need devbox browser on the laptop; a normal dashboard tab has no local app launcher authority. A configured local computer profile supplies the verified alias automatically; --ssh-host <alias> is an explicit override for an alias you have verified for that exact computer. Desktop links do not install the vendor app, authenticate it or bypass organizational restrictions.
Vendor references: Claude Desktop SSH links and Codex desktop commands.