Skip to content

Fix MicroVM guests so claimed pool workers actually connect - #4

Merged
pertschuk merged 1 commit into
mainfrom
fix/lambda-microvm-guest-boot
Aug 21, 2026
Merged

Fix MicroVM guests so claimed pool workers actually connect#4
pertschuk merged 1 commit into
mainfrom
fix/lambda-microvm-guest-boot

Conversation

@pertschuk

Copy link
Copy Markdown
Collaborator

Summary

  • Install the arm64 cursor-agent in the guest image (these Lambda MicroVMs are aarch64; x64 died with Exec format error) and pass the claimed --worker-id.
  • Stop forwarding CURSOR_API_ENDPOINT=https://api.cursor.com into the guest so worker start can exchange the service-account key on api2.cursor.sh.
  • Take controller pool/repo filters from CloudFormation (PoolNames / AllPools / RepositoryUrls) and send guest logs to /aws/lambda/microvms/cursor-pool-worker.

Test plan

  • Start a new agent against the pool this controller serves (lambda-test in the dogfood stack).
  • Confirm controller logs show spawning bc-… as ctrl-… then a MicroVM in RUNNING.
  • Confirm guest CloudWatch /aws/lambda/microvms/cursor-pool-worker shows Authenticated with API key and Private worker started.
  • Confirm GET /v0/private-workers/pools connectedWorkerCount is > 0 and the agent leaves waiting-for-worker.

Made with Cursor

Install the arm64 CLI (these VMs are aarch64), stop forwarding api.cursor.com
as the worker auth host, and pass the claimed worker id. Controller pool/repo
filters now come from CloudFormation instead of a single PoolName.

Co-authored-by: Cursor <cursoragent@cursor.com>
@pertschuk
pertschuk merged commit a9ffc6f into main Aug 21, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant