Run agent builds and tests on remote Windows VMs
My work provides me a Mac laptop plus remote Windows VMs and I've completely stopped using my Mac for agent builds/tests - I give them ssh access to WSL instances and they can go hog wild on the VMs.It's all a bit adhoc - agents still need to pull (or I need to keep the main enlistment up to date on these machines) - I'm thinking of using containers or something else like github actions keep things cleaner, but right now it's "good enough".Regardless I'm pretty happy with how it's working so. Task: My work provides me a Mac laptop plus remote Windows VMs and I've completely stopped using my Mac for agent builds/tests - I give them ssh access to WSL instances and they can go hog wild on the VMs.It's all a bit adhoc - agents still need to pull (or I need to keep the main enlistment up to date on these machines) - I'm thinking of using containers or something else like github actions keep things cleaner, but right now it's "good enough".Regardless I'm pretty happy with how it's working so far. Previously I'd be letting agents do work in the background and they'd kick off builds in the middle of a meeting or something and I'd start dropping video streams until I killed everything.; tools: Codex. Human role: The original post does not say how a person stayed involved.; limitations: The process is described as ad-hoc, requiring manual intervention to keep main enlistments up to date on remote machines. The author considers migrating to containers or GitHub Actions for cleaner management but has not implemented this. Source reliability is secondary, based on a single user comment without detailed technical specifications..
Tools
Published on Agent Work Atlas:
Overview
My work provides me a Mac laptop plus remote Windows VMs and I've completely stopped using my Mac for agent builds/tests - I give them ssh access to WSL instances and they can go hog wild on the VMs.It's all a bit adhoc - agents still need to pull (or I need to keep the main enlistment up to date on these machines) - I'm thinking of using containers or something else like github actions keep things cleaner, but right now it's "good enough".Regardless I'm pretty happy with how it's working so
Workflow
My work provides me a Mac laptop plus remote Windows VMs and I've completely stopped using my Mac for agent builds/tests - I give them ssh access to WSL instances and they can go hog wild on the VMs.It's all a bit adhoc - agents still need to pull (or I need to keep the main enlistment up to date on these machines) - I'm thinking of using containers or something else like github actions keep things cleaner, but right now it's "good enough".Regardless I'm pretty happy with how it's working so far. Previously I'd be letting agents do work in the background and they'd kick off builds in the middle of a meeting or something and I'd start dropping video streams until I killed everything.
Reported result
The author reports satisfaction with the current workflow, noting it is 'good enough' despite being ad-hoc. The primary outcome is the elimination of local resource contention, specifically preventing video stream drops during meetings caused by background builds. No quantitative performance metrics or error rates were provided.
Human role
The original post does not say how a person stayed involved.
Limitations
The process is described as ad-hoc, requiring manual intervention to keep main enlistments up to date on remote machines. The author considers migrating to containers or GitHub Actions for cleaner management but has not implemented this. Source reliability is secondary, based on a single user comment without detailed technical specifications.
Try it
I need to set up a remote build environment for my coding agents. My local machine is a Mac, and I have access to remote Windows VMs with WSL. Please configure an agent workflow where builds and tests run on the remote VMs via SSH instead of locally. First, verify SSH connectivity to [replaceable_input: remote_vm_ip] using user [replaceable_input: vm_username]. Then, ensure the code repository at [replaceable_input: repo_url] is cloned or updated on the remote WSL instance. Run a sample build command [replaceable_input: build_command] on the remote VM and capture the output. Do not execute any destructive commands or modify production data. Present the build logs and resource usage stats to me for approval before automating further steps. If SSH fails, stop and report the error. This is a dry run to confirm the remote execution path works without impacting my local Mac performance.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.