王性驊 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
..
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 screen never runs its own box or VM, from the start	2026-11-09 15:32:36 +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