Antigravity headless runs honored no configured policy at all until 1.1.4
Version 1.1.4 states that headless runs began honoring persisted settings.json policies including permissions, file access, sandbox mode, auto-execution, and artifact review. Before it, every governance control an operator had configured was inert in exactly the mode continuous integration uses. A maintainer post two days earlier announced a narrower fix in 1.1.3, which sat on top of that total non-enforcement.
What this changes for operators
- 1.1.4 is the hard floor for any unattended or CI use of the agy binary. If you ran headless before it, your permissions, sandbox, and artifact review were not applied, so re-audit what those runs were allowed to touch rather than assuming the configuration held.
Featured in
- Assume the Rule Does Not Bind / 2026-07-27
Run: 2026-07-27-weekly-digest-2026-07-02_2026-07-27-frontier-v0
Schema: bitter.frontier_signals.v0 / ID: 2026-07-27-antigravity-headless-honored-no-policy
Research evidence and publication history are open in the repository.