Project Permissions and Agent Authority Record

Project Permissions and Agent Authority Record

Antigravity projects can span multiple folders and carry project-level settings and permissions. Documentation distinguishes local work from isolated worktree mode.

The permissions engine uses Deny, Ask, and Allow lists. Google documents Deny as the highest-precedence rule, followed by Ask and Allow. Unconfigured web browsing, terminal commands, MCP actions, external file access, and other sensitive operations may prompt under documented defaults.

Workspace files are treated differently from non-workspace assets. MCP servers and hooks extend the execution surface. A permission granted to a tool does not prove that the connected system, data, script, or output is safe.

As of July 28, the documentation calls terminal sandboxing a preview on macOS and Linux and says Windows support is coming later. Do not describe all platforms as equally sandboxed.

The durable authority map should name assets, actions, external systems, denials, approval points, isolation, duration, evidence, revocation, and the person authorized to release a consequential result.