Chapter 4. Permissions and Undo — Four Presets, Be Careful with Discard
Required Read this to follow this stage.In One Line: In the app, you pick permissions using four presets (Request Review, Default, Auto, Turbo). Start with Request Review or Default at first. Discard in the Review pane takes effect right away without asking to confirm. The terminal has
/rewind, but your safest net is still your Git history.
Permissions are the range of things the agent may do without asking you. For example, a promise like "Don't ask before editing files in the folder, but always ask before installing a program." We explained why permissions matter in more detail in Claude Code Chapter 4 (optional).
This guide has not yet been tested directly on the app screen. If your screen looks different, follow your screen. This chapter assumes a personal Google account.[1]
Four Permission Presets
| Preset | Running Commands | When to Use |
|---|---|---|
| Request Review | Ask before every command | At first, or for careful tasks |
| Default | Don't ask inside the fence; ask when stepping outside | Once you are comfortable |
| Auto (Preview) | Run safe commands on its own; ask only for risky ones | Experimental feature |
| Turbo | Run everything with no limits | Almost never |
Source: Antigravity official docs (excerpted)[2]
Turbo can read and write your entire computer with no fence.[3] You don't need it for organizing notes.
You can change presets in three places.[4]
- All projects: Settings → General → Global Permissions → Permission Preset
- A single project: Settings → Projects
- Current chat: the permissions picker in the message box
Projects follow your global setting by default (Inherit Global), and you can also set them one by one.[5] This means you can keep a trusted project relaxed and an untrusted folder strict.[6] The official docs do not say which preset a personal account starts with. Check it first when you open the app.
Quick check
Which permission preset in the Antigravity app runs every command without restrictions?
The Fence and Basic Rules
The app has a terminal fence (sandbox, Sandbox). It is a device that limits what the commands the agent runs can touch. The official docs say it is on by default.[7]
However, it depends on the preset.[8]
- On: Default, Auto
- Off: Request Review, Turbo
When the fence is on, commands are limited like this.
- They can only use your workspace folder and temp folders.
- They cannot access the internet.[9]
- Sensitive files (files with passwords or keys) like
~/.sshand.envare also blocked.[10]
For example, say that in Default the agent tries to use a command that downloads something from the internet. That command has to step outside the fence. The app then evaluates the command on its own. Safe, reversible commands proceed without asking, while risky or irreversible commands pause and ask for your approval.[2:1]
Regardless of your preset, there are also basic rules.
- Reading and writing files inside your project folder does not ask. Files outside require approval.[11]
- Reading and interacting with web pages default to "Ask."[12]
- When rules conflict, they are decided in this order: block (Deny) > ask (Ask) > allow (Allow).[13] For example, if you set both "Allow reading web pages" and "Block this site," block wins on that site. You don't need to make any rules right now.
Approvals you give during a chat can stick around, so the agent gradually learns actions it can trust.[14] That is convenient, but remember what you approved.
The terminal (agy) defaults are different. The terminal asks before writing files, running commands, or using web tools[15], and the fence is off by default.[16] We cover this in Chapter 6.
Quick check
How is the command fence (sandbox) set by default in the app's Default preset versus the terminal (agy)?
Undoing Changes
Be careful with Discard in the Review pane. "Discard unstaged changes" is a button that throws away changes you have not yet put on the list to record with git add. This button takes effect right away without asking to confirm, and it even deletes new files that have never been recorded.[17]
The default view also includes edits you made yourself (Chapter 2). So pressing this button can erase not only what the agent changed but also what you changed. Always check what is inside before discarding.
The safest way to undo is your Git history. At this stage, too, we use the same habit as in Codex Chapter 4.
- Before handing off work: save your current state with Git.
- Hand off the task.
- In the Review pane, switch to Agent Edits to view only what changed.
- If it looks good, save again; if not, roll it back.
You don't need to know Git commands. Just ask the agent, "Save the current state with Git" (this is a method we verified in Claude Code; this guide has not yet verified it in Antigravity).
There are other undo features too, but it has not yet been verified whether they also roll back files.
More details (click to expand)
- The terminal has
/rewind(or/undo), which rolls your chat back to an earlier stable state.[18] The name sounds like rewind in Claude Code, but the official docs only say it rolls back the "conversation." They do not say whether it also rolls back files. - The app seems to have an undo feature too. The official changelog mentions that the "Confirm Undo" dialog now has an option to revert only the conversation.[19] However, we could not find docs explaining how to use it, and this guide could not verify it in the app either.
Quick check
Why should you be careful when clicking Discard unstaged changes in the Review pane?
Try It Yourself
- Check your current preset in Settings → General → Global Permissions. If you are new, set it to Request Review or Default.
- Save the current state of your organizer folder with Git.
- Ask the agent to "Add a single line at the very top of the meeting notes from Chapter 2 that says 'Date: today's date'."
- Switch the Review pane to Agent Edits and check the changed line.
What's Next: In Chapter 5, we look at planning (/plan), scheduling (/schedule and Automations), the browser (/browser), and goals (/goal).
Summary
- App permissions have four presets. Start with Request Review or Default, and don't use Turbo.
- The app's fence turns on in the Default and Auto presets and blocks internet access. In the terminal, it is off by default.
- Files inside your project folder don't ask for approval; files outside and web actions do ask.
- Discard in the Review pane deletes changes right away without confirmation. Save with Git before handing off work.
Key Terms
| Term | One-line meaning |
|---|---|
| Permission preset | A bundle that sets your permissions all at once |
| Sandbox | A fence that limits what commands can touch |
| Discard | Throwing away changed content |
/rewind | A terminal command that rolls the chat back to an earlier state |
Finished this chapter?
Progress is saved only in this browser. See your progress on the full table of contents.
Next chapter: Chapter 5. Plan, Schedule, Browser, and Goal
References (20)
This chapter is based on the official Antigravity docs checked on November 1, 2026. This guide has not yet been tested directly on the app screen. Work and enterprise accounts have a different permissions screen.[20] ↩︎
Antigravity official docs, "Agent settings". "Request Review (“Every command requires approval.”): The sandbox is off and every terminal command requires approval." / "Default (“Ask before sensitive operations.”): Commands run without prompting inside the Terminal sandbox; running outside the sandbox requires approval." / "When a command needs to run outside the sandbox, Antigravity automatically evaluates it so safe, reversible commands proceed without prompting while risky or irreversible actions still pause for your approval." antigravity.google (checked on 2026-11-01) ↩︎
Antigravity official docs, "Agent settings". "Turbo (“Run all commands without restrictions.”): All commands run without prompting with no isolation or restrictions, and the agent has full read and write access to your filesystem." antigravity.google (checked on 2026-11-01) ↩︎
Antigravity official docs, "Agent settings". "For all projects: Open Settings > General > Global Permissions > Permission Preset." / "From the message box (
v2.23.0+): Choose a preset from the permissions picker." / "For a single project: Override the global preset under Settings > Projects. Projects default to Inherit Global, which follows your global preset." antigravity.google (checked on 2026-11-01) ↩︎Antigravity official docs, "Agent settings". "Projects default to Inherit Global, which follows your global preset." antigravity.google (checked on 2026-11-01) ↩︎
Antigravity official docs, "Antigravity features". "This means you can have a more permissive setting for a trusted project and a more restrictive security setting for an untrusted folder." antigravity.google (checked on 2026-11-01) ↩︎
Antigravity official docs, "Terminal sandbox". "Antigravity includes a terminal sandbox, enabled by default, that isolates shell commands executed by agents." antigravity.google (checked on 2026-11-01) ↩︎
Antigravity official docs, "Terminal sandbox". "| Default | On | Allowed in sandbox; ask outside |" / "| Turbo | Off | Allowed without prompting, unrestricted |" antigravity.google (checked on 2026-11-01) ↩︎
Antigravity official docs, "Agent permissions". "Default (“Ask before sensitive operations.”): Terminal commands run inside the isolated Terminal sandbox with access restricted to your workspace and temp directories and no network access." antigravity.google (checked on 2026-11-01) ↩︎
Antigravity official docs, "Terminal sandbox". "Sensitive files such as
~/.sshand.envare blocked, anything not explicitly mounted is invisible inside the sandbox, and network access is limited to domains you’ve approved." antigravity.google (checked on 2026-11-01) ↩︎Antigravity official docs, "Agent permissions". "Workspace files: Reading and writing files inside your active project directory is allowed without prompting, while non-workspace files require approval." antigravity.google (checked on 2026-11-01) ↩︎
Antigravity official docs, "Agent permissions". "Web browsing defaults to Ask: Actions for
read_urlandexecute_urldefault to Ask." antigravity.google (checked on 2026-11-01) ↩︎Antigravity official docs, "Agent permissions". "Precedence rule: Conflicting rules are strictly evaluated in priority order: Deny > Ask > Allow." antigravity.google (checked on 2026-11-01) ↩︎
Antigravity official docs, "Antigravity features". "Permissions manually granted during a conversation can persist, allowing the agent to learn trusted actions over time." antigravity.google (checked on 2026-11-01) ↩︎
Antigravity official docs, "Antigravity features". "The default
request-reviewpermission asks before the agent writes files, runs shell commands, or uses web tools, unless one of your allow rules matches." antigravity.google (checked on 2026-11-01) ↩︎Antigravity official docs, "Antigravity features". "The terminal sandbox is off by default." antigravity.google (checked on 2026-11-01) ↩︎
Antigravity official docs, "Review changes". "Discard unstaged changes takes effect immediately, without asking you to confirm. It also deletes untracked files from disk." antigravity.google (checked on 2026-11-01) ↩︎
Antigravity official docs, "CLI best practices". "Type
/rewind(or/undo) to roll back your conversation thread to a previous stable checkout." antigravity.google (checked on 2026-11-01) ↩︎Antigravity official docs, "Changelog". "The Confirm Undo dialog now offers an option to revert only the conversation." antigravity.google (checked on 2026-11-01) ↩︎
Antigravity official docs, "Agent settings". "Business and enterprise accounts use the following settings instead of the permission presets above." antigravity.google (checked on 2026-11-01) ↩︎