AnyBot/deploy/mac
王性驊 ec3fddf3ab A computer showing another brain lets its own box and Lima VM sleep
The Mac mini shows the cloud brain, whose bots work on the brain's own
computer and borrow only this Mac's screen, browser and apps. Its local
box still ran, and the Lima VM under it had grown to its whole 6 GB: the
Mac never gets back memory a VM once used.

- On a screen the box stops after 2 idle minutes, and the Lima VM too when
  nothing else runs in it. probe() no longer starts the VM there, and the
  volume holder and scheduled updates run on brains only. Becoming a brain
  again starts both (probe/ensure_running already wake the VM).
- Screen mode is decided from the settings before the box loop's first
  look, which used to start the VM at launch.
- gvisor-vm.sh: 4 GB instead of 6 (box capped at 2 GB), and the VM's
  ModemManager, udisks2 and multipathd are turned off.

Verified on this Mac: box and VM stopped by themselves 2 minutes after the
app started; the VM process (4.4 GB plus compressed pages) is gone.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Uirha5F5gJt93t3yEx3XcS
2026-11-09 15:24:28 +08:00
..
bundle.sh Mac permissions: ask at most every ten minutes; one fixed signing key keeps them across updates; open apps by their shown name 2026-11-05 16:57:44 +08:00
com.anybot.relay.plist AnyBot: first commit of the working desktop app 2026-11-04 16:51:51 +08:00
com.anybot.serve.plist AnyBot: first commit of the working desktop app 2026-11-04 16:51:51 +08:00
gvisor-migrate.sh Checked by using it: tests stay off the real box, gVisor scripts run clean, times are the person's 2026-11-07 00:19:56 +08:00
gvisor-vm.sh A computer showing another brain lets its own box and Lima VM sleep 2026-11-09 15:24:28 +08:00
sign.sh Mac permissions: ask at most every ten minutes; one fixed signing key keeps them across updates; open apps by their shown name 2026-11-05 16:57:44 +08:00