Evidence record / antigravity
A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.
2026-09-21-antigravity-remote-control-grew-into-a-boot-persistent-service-and-remote-triggered-turns-ran-without
Remote Control grew into a boot-persistent service, and remote-triggered turns ran without the session’s permission mode until 1.2.6. Capability: a machine can now be left reachable for remote agent control across reboots. Defect: before 1.2.6 (the note gives no start version; --remote-control already existed at 1.1.19), a turn started remotely did not carry the local session’s permission mode, cycle mode, or outside-workspace grants. The note does not say what it ran under instead.
Channel: tagged-release. Half: both. Date: 2026-09-03 (tunnel hardening), 2026-09-10 (service), 2026-09-18 (permission fix).
Operator consequence: Do not run the 1.2.0 background service below 1.2.6; if you used Remote Control before 1.2.6, treat remote-triggered turns in that span as having run under an unknown permission posture and review their transcripts. On >= 1.2.6, remote-control status belongs in your host inventory: it is a persistent inbound control path. Prefer the session-scoped form unless you need reboot survival.
Receipt
Finding metadata
Run: 2026-09-21-weekly-digest-2026-08-20_2026-09-21-frontier-v0
Finding ID: 2026-09-21-antigravity-remote-control-grew-into-a-boot-persistent-service-and-remote-triggered-turns-ran-without
Profile citations
- Antigravity CLI / claim / remote-control-permission-mode
Source links
Primary links, including exact changelog lines when available.
Versioned source: run artifact