Desktop-managed SSH environments
Remote access and devices
The desktop app can start or reuse a T3 Code server on a remote host over SSH and open the port forward for you. Projects, provider credentials, and agent work stay on the remote machine.
T3 Code docs: remote access
What it’s for
Working on a Linux host or Apple Silicon Mac over SSH, where T3 Code starts or reuses a server and opens the port forward for you; the first launch downloads T3 Code's server to the host.
T3 Code docs: remote access
How to use it
Open Settings → Environments → Add environment, choose SSH, and enter a host or SSH alias such as user@example.com.
T3 Code docs: remote access
Confirm provider CLIs are on the non-interactive login PATH with ssh user@example.com 'sh -lc "command -v claude codex"'.
T3 Code docs: remote access
Expect the first launch to be slower while the server downloads to ~/.t3/runtime; if reconnecting fails after an app update, retry once.
T3 Code docs: remote access
Theo’s tips
Once you have an end-to-end flow that works for a class of bug, use T3 Code's remote machine management to spin up many threads across several machines and run the work in parallel.
…about setting up a cloud environment or, I don't know, using something like T3 Code and the remote machine management stuff. Once you have an end-to-end flow that is working for figuring out a class of issue or bug, you can spin up a bunch of threads on a bunch of instances on a bunch of machines and immediately parallelize it.
What’s changed
- SSH hosts are suggested in a dropdown under the host field.Updated Sep 3
Unofficial notes. Not affiliated with Theo or t3.gg.