Replace --dangerously-skip-permissions with per-path allows in settings.json
Antigravity 1.5.2 no longer auto-approves protected commands or out-of-workspace access under --dangerously-skip-permissions. Grant one path at a time via Allow access to this file? or settings.json, and invoke cloud plugin skills in --remote-agent with /skills.Why this loop
1.5.2 changes --dangerously-skip-permissions so commands on the built-in protected list are no longer approved automatically and go through the usual checks; every other command still runs without asking. When a Gemini Enterprise administrator requires review, that flag and plugin agents set to auto-allow no longer approve terminal commands or file access outside the workspace, and headless runs deny those requests. The outside-workspace prompt is now Allow access to this file? and can always allow or deny that one path for the conversation or in settings.json, instead of turning on access to everything outside the workspace. Subagents no longer stall about 60 seconds on those checks, and headless agy -p with the flag no longer waits on remaining interaction, while explicit deny rules still apply. Teams that used the flag in CI or agent loops will see extra prompts or denials unless they pin only the paths they need. Cloud plugin skills from /plugin now appear in --remote-agent sessions in the / menu, as a typed prefix, and under Remote agent skills in /skills; /skills reload lists them again. Plugins and skills in .agents/plugins.json and .agents/skills.json load only from inside the workspace or repository root; absolute paths, ../, and symbolic links are skipped.
Proposed actions
- When Antigravity 1.5.2 shows
Allow access to this file?, always allow or deny that one path for this conversation or in settings.json. Do not grant access to everything outside the workspace. - Remove
--dangerously-skip-permissionsfrom agy aliases, CI, andagy -pscripts. Protected commands now go through the usual checks; if a Gemini Enterprise admin requires review, headless runs deny terminal commands and file access outside the workspace instead of auto-approving. - In a
--remote-agentsession, connect cloud plugins with/plugin, run/skills, and confirm they are grouped underRemote agent skills. Type a skill at the start of a message. After connecting plugins, run/skills reload. - Rewrite every entry in
.agents/plugins.jsonand.agents/skills.jsonto a path inside this workspace or its repository root. Remove absolute paths,../, and symbolic links—1.5.2 skips those. - On macOS, use Option-key shortcuts such as
alt+mwithout setting Option to act as Alt. Only if you need the old character-insert behavior (for exampleµ), run:export AGY_CLI_MAC_OPTION_AS_ALT=0
Agent prompt
Paste into your agent or query via MCP (get_agent_prompt) — free, no extra AI costGoogle Antigravity / agent task
DevAgentRadar → Google Antigravity
Goal: turn this release signal into a safe pilot plan for my stack.
Context
Assistant: Google Antigravity Proposal: Replace --dangerously-skip-permissions with per-path allows in settings.json Summary: Antigravity 1.5.2 no longer auto-approves protected commands or out-of-workspace access under --dangerously-skip-permissions. Grant one path at a time via Allow access to this file? or settings.json, and invoke cloud plugin skills in --remote-agent with /skills. Primary source: https://github.com/google-antigravity/antigravity-cli/releases/tag/1.5.2
Why it matters
1.5.2 changes --dangerously-skip-permissions so commands on the built-in protected list are no longer approved automatically and go through the usual checks; every other command still runs without asking. When a Gemini Enterprise administrator requires review, that flag and plugin agents set to auto-allow no longer approve terminal commands or file access outside the workspace, and headless runs deny those requests. The outside-workspace prompt is now Allow access to this file? and can always allow or deny that one path for the conversation or in settings.json, instead of turning on access to everything outside the workspace. Subagents no longer stall about 60 seconds on those checks, and headless agy -p with the flag no longer waits on remaining interaction, while explicit deny rules still apply. Teams that used the flag in CI or agent loops will see extra prompts or denials unless they pin only the paths they need. Cloud plugin skills from /plugin now appear in --remote-agent sessions in the / menu, as a typed prefix, and under Remote agent skills in /skills; /skills reload lists them again. Plugins and skills in .agents/plugins.json and .agents/skills.json load only from inside the workspace or repository root; absolute paths, ../, and symbolic links are skipped.
Suggested actions
- When Antigravity 1.5.2 shows
Allow access to this file?, always allow or deny that one path for this conversation or in settings.json. Do not grant access to everything outside the workspace. - Remove
--dangerously-skip-permissionsfrom agy aliases, CI, andagy -pscripts. Protected commands now go through the usual checks; if a Gemini Enterprise admin requires review, headless runs deny terminal commands and file access outside the workspace instead of auto-approving. - In a
--remote-agentsession, connect cloud plugins with/plugin, run/skills, and confirm they are grouped underRemote agent skills. Type a skill at the start of a message. After connecting plugins, run/skills reload. - Rewrite every entry in
.agents/plugins.jsonand.agents/skills.jsonto a path inside this workspace or its repository root. Remove absolute paths,../, and symbolic links—1.5.2 skips those. - On macOS, use Option-key shortcuts such as
alt+mwithout setting Option to act as Alt. Only if you need the old character-insert behavior (for exampleµ), run:export AGY_CLI_MAC_OPTION_AS_ALT=0
Config surfaces this release may change
- background and headless runs (high confidence) — check your repo before applying
- permission rules (high confidence) — check your repo before applying
- settings files (high confidence) — check your repo before applying
- skills (high confidence) — check your repo before applying
- subagent definitions (high confidence) — check your repo before applying
- MCP servers — check your repo before applying
After you finish
Do not report this as applied to DevAgentRadar. You cannot write the visitor's loop.
Tell the human: open https://devagentradar.com/proposals/google-antigravity-1-5-2-replace-dangerously-skip-permissions-with-per-p and mark Applied, Skipped, or Failed. Proposal id: 8b1f114a-507d-40e2-911e-3ef764e8d60e
Please:
- Map the change to concrete pilot steps
- Flag security / permission implications
- Keep the pilot reversible
Your loop
This browser · no sign-in · not shared as “you”After you run the prompt
Only you can mark this. Agents cannot write your loop.
Your decision stays on this device. A public tally appears after a few votes.