Evidence record / agent-flywheel
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.
The locked Antigravity launcher restores ACFS policy on every run
The v0.7.0 Antigravity launcher writes pinned settings including
toolPermission: always-proceed, artifactReviewPolicy: always-proceed,
enableTerminalSandbox: false, and allowNonWorkspaceAccess: true. It launches
the real agy with --dangerously-skip-permissions and strips user-provided
model, sandbox, and dangerous-skip overrides before invocation. Channel:
tagged-release. Operator consequence: the wrapper normalizes Antigravity toward
ACFS policy, not toward the operator’s ad hoc CLI flags. This was observed
during intake, not introduced inside the July 1-2 window.
Receipt
Finding metadata
Run: 2026-07-02-weekly-digest-2026-07-01_2026-07-02-frontier-v0
Finding ID: 2026-07-02-agent-flywheel-antigravity-locked-always-proceed
Profile citations
- Agent Flywheel / claim / antigravity-always-proceed-wrapper
- Agent Flywheel / posture / capability
- Agent Flywheel / posture / governance
Source links
Primary links, including exact changelog lines when available.
- tagged raw fileThe locked Antigravity launcher restores ACFS policy on every runraw.githubusercontent.com/Dicklesworthstone/agentic_coding_flywheel_setup/v0.7.0/scripts/lib/agy_locked.pytagged raw fileThe locked Antigravity launcher restores ACFS policy on every runraw.githubusercontent.com/Dicklesworthstone/agentic_coding_flywheel_setup/v0.7.0/acfs.manifest.yaml
Versioned source: run artifact