AnyBot/deploy
王性驊 c5bb16750f A screen never runs its own box or VM, from the start
The person wants the local box and Lima VM off whenever this AnyBot is set
to show another brain, not stopped after two idle minutes.

- sleep_on_a_screen has no idle wait and also runs right at start, before
  the loop's first 20-second pause; a resume of an interrupted rebuild is
  done on brains only (it would start the box on a screen).
- gvisor-vm.sh no longer registers the VM to start with the Mac: AnyBot
  starts it itself when it is the brain and wants its computer.

Verified on this Mac: VM started by hand while AnyBot was closed; the new
AnyBot (a screen of the cloud brain) stopped it 4 seconds after launch.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Uirha5F5gJt93t3yEx3XcS
2026-11-09 15:32:36 +08:00
..
ci Release builds on Gitea Actions: macOS app, Ubuntu, headless Linux, server 2026-11-04 22:07:46 +08:00
linux Remove what nothing uses and keep one copy of what was written several times 2026-11-05 23:21:47 +08:00
mac A screen never runs its own box or VM, from the start 2026-11-09 15:32:36 +08:00
server HTTPS on the local network's own IP, with a certificate the server signs itself 2026-11-07 21:27:07 +08:00
test E2E: remote screenshot, click and typing; a Linux Wayland run with a full runtime folder 2026-11-05 20:28:52 +08:00