agy auto mode,
and what it still asks.
Start Antigravity CLI with agy --mode auto, or press Shift+Tab until the mode reads Auto. Auto mode approves file edits and safe commands without asking. It still asks before irreversible actions, and a command that would leave the terminal sandbox is checked by a separate reviewing agent first. agy has no YOLO mode under that name: the no-prompt switch is --dangerously-skip-permissions.
Updated
Featured on Hacker NewsTurn on Auto mode
Three ways, from one session to every session.
Step 1
Start a session in Auto mode
Run agy --mode auto. The flag applies to that session and overrides your saved mode.
Step 2
Or switch inside a session
Press Shift+Tab to cycle default, accept-edits, auto and plan, or pick Auto under Agent Mode in /config. Auto is skipped where it is not available.
Step 3
Make it the default
Choose Auto under Agent Mode in /config, or set "agentMode": "auto" in ~/.gemini/antigravity-cli/settings.json.
{
"agentMode": "auto"
}agentMode also takes accept-edits and plan. Leave it out for the default mode.
The four agy modes
default needs no flag. --mode takes the other three. Auto mode is in Preview.
| Mode | Runs without asking | Still asks |
|---|---|---|
default agy | Reading files in the workspace, and anything an allow rule in /permissions covers. | File edits and new files, with a diff to review, and terminal commands. |
accept-edits agy --mode accept-edits | File edits and new files inside the workspace. | Terminal commands, and edits outside the workspace. |
auto agy --mode auto | Workspace file edits, commands inside the terminal sandbox, and commands outside it that a reviewing agent judges safe and reversible. | Irreversible or high-risk actions, such as destructive Git and file commands. Web, MCP and outside-the-workspace actions keep their default, which is to ask. |
plan agy --mode plan | Analysis. agy outlines the steps before it writes any code. | The plan waits for your review before agy goes ahead, unless you change Artifact Review in /config. |
When agy says auto mode is not available
agy prints one line and carries on in the default mode, so it is easy to miss.
$ agy --mode auto
warning: --mode auto is not available for this account; continuing in the default mode.Account
Auto mode is in Preview, and Google's docs say it is not currently available for business or enterprise accounts. That matches the warning's wording. Turning the terminal sandbox on does not change it: on our Mac, agy 1.4.12 printed the same line with the sandbox on.
Version
Auto mode arrived in agy 1.3.5 on 14 October 2026 for macOS and Linux, and in 1.4.4 on 21 October for Windows. Run agy update, then agy --version.
Sandbox
Auto mode needs the terminal sandbox. On Windows that means Windows 11 version 24H2 or later with the August 2026 update. On Linux the sandbox needs unprivileged user namespaces. Where it cannot run, agy stops offering modes that need it.
How the Auto mode review has changed
Auto mode shipped in agy 1.3.5. Six releases since have changed what the reviewing agent lets through.
| 1.3.6 | Allows the workspace's own format, lint and fix commands. Blocks commands that would upload sensitive data. |
| 1.4.3 | Subagents and custom agents get the same review, instead of asking about every command that leaves the sandbox. |
| 1.4.4 | Takes agy's own question into account when you reply with a short answer like yes, checks every command in a pipeline, and prompts before destructive Git or file commands. |
| 1.4.7 | Asks less often about routine commands, such as cleaning up temporary files, stopping a local process or running a formatter. |
| 1.4.8 | Stops any single slow check after 10 seconds, so the review times out less often. |
| 1.4.9 | Knows whether the working folder is a Git or other repository, so it stops running git status where there is none and times out less often. |
Is there an agy YOLO mode?
Not under that name. Both guesses fail.
$ agy --yolo
flags provided but not defined: -yolo
$ agy --mode yolo
warning: unrecognized --mode value "yolo" (valid: accept-edits, auto, plan)The no-prompt switch is agy --dangerously-skip-permissions for one session, or toolPermission set to always-proceed in /config for every session. Neither has a reviewing agent. Only your own ask and deny rules still stop a call. How the flag and the presets work.
Auto mode decides for you. Pushary asks you.
In Auto mode a reviewing agent picks which commands are safe. Some people want that call back. Pushary connects to agy through its hooks and sends each risky call to your phone. You answer yes or no, and every answer is recorded.
One command
npx pushary@latest setupIf you never chose a tool permission preset, setup sets toolPermission to always-proceed so Pushary is the only gate, and disconnecting puts it back. always-proceed overrides Auto mode, so the reviewing agent stays out while that setting is on.
Decide the risky calls yourself.
Your rules let the safe ones run. The rest wait for your yes or no on your phone.
Start your trial$9.99/mo after a 3-day free trial. Cancel anytime.
agy auto mode questions
What does agy auto mode still ask before running?
Irreversible or high-risk actions. Workspace file edits and commands inside the terminal sandbox run without a prompt. A command that would leave the sandbox goes to a separate reviewing agent first, which lets safe, reversible ones through and sends the rest back to you. Since 1.4.4 that includes destructive Git and file commands. Web reads, MCP tools and files outside the workspace keep their default, which is to ask.
Why does agy say --mode auto is not available for this account?
Auto mode is in Preview, and Google's docs say it is not currently available for business or enterprise accounts. agy prints the warning and carries on in the default mode. On a personal account, check the version and the platform: Auto mode needs agy 1.3.5 on macOS or Linux, or 1.4.4 on Windows 11 version 24H2 or later, because it depends on the terminal sandbox.
How do I make agy start in auto mode every time?
Pick Auto under Agent Mode in /config, or set "agentMode": "auto" in ~/.gemini/antigravity-cli/settings.json. The same key accepts accept-edits and plan. Leave it out to stay in the default mode. --mode on the command line overrides the saved value for one run, and --settings takes a JSON object that agy never writes back.
What is the difference between agy auto mode and --dangerously-skip-permissions?
Auto mode keeps a gate: a reviewing agent decides which commands are safe, and irreversible ones come back to you. --dangerously-skip-permissions has no reviewer. It puts the session in always-proceed, so every tool call runs without a prompt unless one of your own ask or deny rules matches. Since agy 1.3.2 it no longer approves the implementation plan in plan mode.
How do I run agy in YOLO mode?
agy has no mode or flag by that name. agy --yolo stops with flags provided but not defined, and --mode yolo prints a warning listing the real values. What people mean by YOLO is agy --dangerously-skip-permissions for one session, or toolPermission set to always-proceed in /config for every session. Gemini CLI's own YOLO switch is --approval-mode=yolo.
Do my /permissions rules still apply in auto mode?
Yes. Allow, ask and deny rules take precedence in every mode, and so do the strict preset and --dangerously-skip-permissions. A deny rule still blocks a command that Auto mode would have run, and strict brings back a prompt before every tool action, file reads included, which overrides Auto mode.
Does Pushary work with agy auto mode?
Not side by side. If you never chose a tool permission preset, connecting Pushary sets toolPermission to always-proceed, and Google's docs say always-proceed overrides Auto mode. Your Pushary rules then decide which calls run on their own instead of agy's reviewing agent, and each risky call waits for a yes or no on your phone. Every answer is recorded, with your name when you answer in the Pushary app. Disconnecting puts your setting back.