Playbooks · Coding tasks
Antigravity CLI 1.5.7: Auto becomes the default
Written November 12, 2026
In 1.5.7, Auto is the default Agent Mode and strict permissions finally override looser settings. What changes on your next run.
The new default
The 1.5.7 release notes change the default Agent Mode from Default to Auto. Sessions with no saved mode now start in Auto wherever Auto mode is available, and in Default where it is not. That includes headless agy -p runs, which matters for anyone scripting the CLI: a script that saved no mode wakes up under Auto's rules, approving workspace edits and running sandboxed commands without asking, with risky actions still prompting. To keep the previous behaviour, choose Default for Agent Mode in /config, which saves "agentMode": "" to settings.json.
This is a default change, not a new mode. Auto mode arrived for ACP sessions in 1.5.4, and 1.5.5 previewed /swarm. Version 1.5.7 is about what a fresh session starts in, and about which permission setting wins when settings disagree.
Strict wins
A Tool Permission setting of strict now takes precedence over Auto and accept-edits modes, so file edits still ask for approval under strict even when the session mode would otherwise approve them. Two related holes close in the same release. A PreToolUse hook returning auto_approve, or a wildcard command(*) allow rule, can no longer bypass an organization's admin-enforced review: commands that would leave the terminal sandbox, commands the admin policy holds for review, and file reads or writes outside the workspace under an “always ask” file-access policy now always ask. And saved command allow and deny rules are no longer ignored when an admin policy requires the terminal sandbox but the machine has no OS sandbox; your saved rules now apply, and unlisted commands still ask before running.
The freeze and sign-in fixes
- Long-line freezes. A command printing a very long line without spaces could freeze the interface for several seconds and stall streaming and window resizing. Line wrapping now takes time proportional to the line's length.
- Stalled replies. Agent replies could stall for 20 seconds or more while a group of tool calls with long output was still animating its token counts. Streamed steps now keep appearing while the group re-renders.
- Background commands waiting for input. The agent could miss that a backgrounded command was waiting at a password or yes/no prompt printed before it went to the background. The agent is now notified once that output settles.
- Windows sign-in. Browser sign-in on Windows could fail because the CLI's local sign-in callback listened on only IPv4 or IPv6 while the browser redirected over the other. The callback now listens on both.
- Carbon through a gateway. Gemini 4 Carbon requests through an enterprise model gateway could fail with a “Thinking budget is not supported for this model” error. The CLI now sends Carbon a thinking level and no longer leaves the Low, Medium, or High suffix in the model ID it sends to the gateway.
Limits
- Auto is the default only where Auto mode is available. Where it is not, a session with no saved mode still starts in Default.
- The release changes starting behaviour for sessions with no saved mode. If you want the old start under any saved setup, set Agent Mode to Default in
/configrather than assuming a flag on one run carries over. - Strict precedence covers file edits under a
strictTool Permission setting. It is a precedence rule for that setting, not a promise that every action in an Auto session asks first.
Related playbooks
- Antigravity CLI 1.5.4: ACP Auto mode
- Kiro CLI 3.0: V3 is the default, Classic is gone
- Paperclip: native Runner now default
- Your Work default changed to Terra: check your preset and pick Sol back for the hard jobs
Sources
Back to: Coding playbooks hub · Also: Antigravity CLI 1.5.5: swarms in preview · Antigravity CLI 1.5.4: ACP Auto mode