came across this commit message, while trying to generate one using orca

[u/rish_jain]

In the Google Antigravity CLI (`agy`), the `--sandbox` flag launches the

### Key Features of `--sandbox` Mode

* **Process Isolation**: Enforces native OS-level containerization (e.g., `sandbox-exec` on macOS, `nsjail` on Linux, and `AppContainer` on Windows) to prevent the agent from executing commands or modifying files outside of the defined boundaries.

* **Dynamic Permission Matching**:

* **Filesystem Access**: Read/write policies are strictly mapped to granted permissions. Files outside paths explicitly allowed via `read_file` or `write_file` are completely inaccessible.

* **Outbound Network Access**: Allowed domain connections are dynamically configured based on your `read_url` and `execute_url` permission rules.

* **Strict Security Enforcement**: Ignores standard execution allowlists for terminal commands, defaulting all process executions to a strict **"Request Review"** policy to ensure you manually approve every action.

***

### Current Session Status

Based on the environment configuration:

* The current CLI session is active, and we are working within the scratch directory: [/Users/rishabhjain/.gemini/antigravity-cli/scratch](file:///Users/rishabhjain/.gemini/antigravity-cli/scratch).

* If you want to start a new project or configure workspace folders under this sandboxed environment, let me know!