You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature]: Remote desktop targets (Windows, macOS, Linux) as device hosts, so any machine can run and test the desktop heads it can't build #37333
T3 Code's device hosts let me reach iOS simulators on a Mac from Ubuntu and Windows over SSH, and every machine already has Android. That covers the mobile heads. The remaining gap is the desktop heads.
For a cross-platform app (in my case Flutter, but this applies to Tauri, Electron, Avalonia, .NET MAUI and so on), each OS can only build and run its own desktop target:
Windows needs to test the macOS and Linux desktop builds.
macOS needs to test the Windows and Linux desktop builds.
Linux needs to test the macOS and Windows desktop builds.
I'd like to add a Windows, macOS or Linux machine as a desktop device host, the same way an SSH device host works today. A thread on any machine could then pick "Linux desktop on jhancock-ubuntu" or "macOS desktop on mac" as a target, and the agent would get full testability there: build, launch, screenshot, read UI, tap and type, and read logs.
Why this is close to possible already
Run:ssh <host> 'cd repo && flutter run -d linux' (or -d macos, -d windows) builds and launches the app on the remote machine.
Test: Flutter testing MCPs such as marionette_mcp, flutter_skill and flutter_agent_lens only need the Dart VM service URI. Forwarding that port with ssh -L gives an agent on another machine full widget-level control and inspection.
What's missing is T3 wiring this up as a first-class device, the way it does for simulators: discover the remote host's desktop targets, sync or point at the worktree there, build and launch, tunnel the VM service (or another app-specific debug or automation port) back to the thread, attach the testing MCP, show a live preview or snapshot in the device panel, and release the device when the thread settles.
Proposed shape
Device source: "Remote desktop (SSH)." Reuse the existing SSH device-host setup and probe the host for its OS and available desktop toolchains (flutter devices, dotnet, cargo tauri, and so on).
Worktree on the remote: either a remote T3 environment that already owns the repo (preferred), or rsync or git-push of the thread's worktree to a scratch path.
Launch and attach: start the app on the remote, capture the VM service or debug URI from stdout, ssh -L it back, and hand it to the thread's MCP tools (marionette, flutter_skill, flutter_agent_lens) as if the app were local.
Visibility: window snapshots through agentcast or the computer-use driver on that host, shown in the device panel like the simulator preview.
Locking and approvals: the same DEVICE_IN_USE semantics, cleanup on settle, and access-mode-gated approvals as existing devices.
My setup
Three machines (macOS M4 Pro Max, Ubuntu, Windows), all on the LAN with key-only SSH between them, all with T3 Code. iOS on Ubuntu and Windows through the Mac device host works great. With this feature, every machine could test all five heads (iOS, Android, macOS, Windows, Linux) from one thread.
Thanks for writing this up. It asks for new behaviour rather than reporting a defect, so it does not belong in the bug tracker and I'm closing it as not planned here. Feature ideas are discussed in Discussions: please post it there.
Activity
juliusmarminge commentedon Nov 15, 2026
Thanks for writing this up. It asks for new behaviour rather than reporting a defect, so it does not belong in the bug tracker and I'm closing it as not planned here. Feature ideas are discussed in Discussions: please post it there.