Run agent builds and tests on remote Windows VMs

A developer gives coding agents ssh access to WSL instances on remote Windows VMs to run builds and tests instead of on their Mac laptop.

What They Did: The developer's employer supplies a Mac laptop plus remote Windows VMs. The agents get ssh access to WSL instances on those VMs and run their builds and tests there. Setup is ad hoc: agents have to pull the latest code, or the developer keeps the main enlistment current on each machine.
How It Went: Builds no longer run on the Mac, so background agents stop causing video streams to drop during meetings. The developer is happy with it, though the setup is only good enough for now.
Worth Knowing: Keeping code in sync on the VMs is manual; the developer is considering containers or GitHub Actions to make it cleaner.

Try it yourself with Codex

I'm working in [project folder] on my [Mac/Linux] machine, but builds and tests must run on a remote Windows machine. You can reach it with ssh at [user@host] and use WSL there. Sync the code to [remote path], run [build command] and [test command] over ssh, and report which tests passed and failed with the relevant error output. Do not delete or overwrite anything on the remote machine outside [remote path], and show me any command that would do so before running it.

Read the original ↗