Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

Antigravity 1.5.2 tightens headless permissions

Written November 7, 2026

Antigravity CLI 1.5.2 stops --dangerously-skip-permissions auto-approving protected commands in headless runs. What breaks in CI — and the fix.

What changed

Antigravity CLI 1.5.2, released November 6, 2026, changes what --dangerously-skip-permissions approves. Commands on the system command denylist are blocked instead of approved automatically, while every other command still runs without asking. That is the change most likely to show up as a broken pipeline: a headless job that used to sail through now stops on the denylisted commands it used to get for free.

The same release tightens the flag a second way. When a Gemini Enterprise administrator requires terminal commands or file access outside the workspace to be reviewed, --dangerously-skip-permissions — and plugin agents set to auto-allow — no longer approve those either, and headless runs deny such requests instead of waiting on them. The release notes also fix the opposite failure: subagents used to stall for about 60 seconds on file permissions under the flag, and headless -p runs with the flag no longer wait on any remaining interaction, while explicit deny rules still apply.

Three more changes ship in 1.5.2. Skills from the cloud plugins connected with /plugin now work in --remote-agent sessions: they appear in the / menu, /skills lists them grouped by plugin under Remote agent skills, and /skills reload lists them again. On macOS, Option-key shortcuts such as Alt+M now work out of the box without setting Option to act as Alt in the terminal; AGY_CLI_MAC_OPTION_AS_ALT=0 restores the old behaviour. And the prompt shown when the agent asks for access to a file outside the workspace now reads "Allow access to this file?" and offers to always allow or deny that one path for the conversation or in remote settings, instead of turning on access to everything outside the workspace. Plugin installs also got stricter: agy plugin import, install, uninstall, enable, and disable reject plugin names that are not safe file names and refuse to write outside the plugins folder or through symbolic links, so an imported plugin can no longer overwrite other configuration files such as mcp_config.json.

What breaks in CI

A scheduled agy -p job that relied on the flag to approve everything will now fail on any denylisted command it calls, and on any terminal command or outside-workspace file access an Enterprise administrator requires to be reviewed. The failure looks like a broken pipeline, not a permission change: the job exits without completing the step, and nothing in the output says the CLI changed its mind. On an Enterprise-managed machine the same job may also start denying requests it used to get approved, with no prompt anywhere to answer, because headless runs cannot pause to ask.

Steps

  1. Upgrade, then run each scheduled job once by hand. Update to 1.5.2 and run every scheduled agy -p job once while you watch it. Write down each command the run denies. That list is the whole migration: every denied command is a permission the job needs, stated explicitly.
  2. Allow exactly the denied commands. Add scoped allow rules for the commands from step 1 to the job's permissions, so the job approves the commands it needs and nothing else. Keep the rules narrow: a rule for one command and one path, not a rule for a whole directory of commands.
  3. Do not widen the bypass to paper over it. The deny is the intended change, not a bug in the release. Adding a broader bypass, or moving the job to a machine without the Enterprise review requirement, restores the old behaviour by removing the control that caught the denylisted command. Fix the allow list instead.
  4. Check the outside-workspace prompt. If a job touches files outside the workspace, expect the new "Allow access to this file?" prompt in interactive runs, and grant access for that one path only. A job that needs the same path every run belongs in settings.json, not in a per-conversation grant.
  5. Re-run the schedule. Run the full schedule once more after the allow-list edits. A clean run with no denials is the sign the migration is done. Keep the denied-command list from step 1 with the job, so the next person who edits the job knows which commands it depends on.

What can go wrong

Limits

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Google Jules ends Nov 11: export your work · Vet an Antigravity plugin before the one-click install · What broke in agent tools this week