Support for remote sandboxed environments.

[Teebor-Choka]

I could not find, whether t3 supports the remote sandboxed enviornments, AKA "track on your mac what is happening in a multiple remote sandbox VMs".

[shurkanTwo]

Yes — in v0.1.0 you can use the Mac desktop app to work with multiple remote environments.

For existing VMs, the direct route is:

1. Open Settings → Connections → Add environment → SSH.
2. Enter the VM's SSH host or alias, such as user@my-vm.
3. Repeat for the other VMs.

T3 Code starts or reuses its server on each host and sets up the port forward. Projects, provider credentials, and agent work stay on the remote machine. The v0.1.0 SSH documentation lists the host requirements: Linux or Apple Silicon macOS, the download/extraction utilities, and the provider CLI available in a non-interactive login shell.

T3 Connect is another option: run t3 connect on each host, complete setup, and sign into the same account on the Mac. The host server must remain running; the CLI offers a background service, or you can run t3 serve.

That covers following and controlling work across your remote VMs. You still provision the VMs yourself, and their configuration supplies the sandbox/isolation.

[Teebor-Choka]

Will there be a interface to implement arbitrary sandbox solutions? Not just the ones using SSH?

[shurkanTwo]

If you mean a pluggable interface for creating and managing arbitrary sandbox backends, I haven’t found a documented public API or a confirmed commitment to ship one.

There’s an existing proposal specifically for that: #18019 — external sandbox broker. It requests a provisioning hook that returns connection details, with providers such as Boat and Daytona as examples. It hasn’t received a maintainer answer yet.

There’s also concrete work beyond SSH: Theo’s Docker sandbox PR #15350. It’s currently unmerged and Docker-specific, so it doesn’t establish a general sandbox extension API.

For connecting to an environment you provision yourself, SSH already isn’t required: a running T3 server can be reached through direct pairing or T3 Connect. Having T3 provision and manage that environment through your own backend is the additional capability proposed in #18019. A maintainer would need to confirm plans for that.

[shurkanTwo]

@Teebor-Choka does this cover what you were looking for? If so, could you mark the reply that helped as the answer, so others asking about remote sandboxes find it faster? If something is still open, let me know and I'll dig further.