Move builds and tests to a remote Windows VM

A developer had Codex run builds and tests over SSH on WSL in remote Windows VMs instead of using their Mac laptop.

Done with Codex· Intermediate· Oct 2026

What they did
Their employer issued a Mac laptop and separate Windows virtual machines. The developer let Codex connect by SSH to WSL on those machines so it could fetch code and carry out build and test commands there. The workflow was improvised: either the agent updated its own checkout, or the developer kept the main copy of the code current on each machine.
How it went
That shifted the heavy work off the Mac, which prevented background agents from dropping video streams during meetings. The developer was pleased, but also called the arrangement a stopgap.
Tips
If you try this, expect to spend time keeping the checkouts aligned by hand. Containers or GitHub Actions may be a cleaner long-term option.

Try it yourself with Codex

I need [Codex] to work against a remote Windows VM through WSL instead of on my local machine. Use ssh with [user@host] to reach it, put the code under [remote path], then run [build command] and [test command]. Before you do anything that would send, delete, overwrite, or submit data, pause and ask for my approval. When you're done, tell me which tests succeeded, which failed, and show the relevant error output.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on news.ycombinator.com ↗

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.