“Antigravity uses a robust, unified permission engine to secure your environment while enabling autonomous workflows.”
However, when I switch to the CLI tab in the documentation, it says:
“Permissions are evaluated across three distinct access lists configured inside your global settings (~/.gemini/antigravity-cli/settings.json)”
When I edit that specific settings.json, the changes do not impact the Antigravity Desktop App permissions when I go check, which brings me back to my initial question.
After digging into local storage, it looks like the Desktop App reads global permissions from ~/.gemini/config/config.json (under userSettings.globalPermissionGrants), while the CLI reads from ~/.gemini/antigravity-cli/settings.json, and project-level permissions are stored separately in ~/.gemini/config/projects/<project-id>.json.
Is this separation between the CLI and App intended behavior, or is there supposed to be like I guess a sync layer between them that I am missing?
I am also asking because it would be really nice if we could just point an agent at a specific file (or unified config path) where permissions are stored for both project and global settings and make edits there, rather than having to manually track down and manage different files across separate directories (or deal with the manual config setup Antigravity currently imposes on both the app and CLI).
Has anyone else run into this, or figured out the intended way to keep both in sync?
The correct (IMO) place for configs is /.gemini/config/config.json
For the CLI, projects seem unless you will always launch the CLI with project parameters (which seems stupid to me). Non-CLI knows what project it is based on path, but CLI does not, so I ignore projects permissions (for a machine on which I have a billion of them) and try to make do with the global config.
the globalPermissionGrants → allow is also substantially broken in my experience; non-regex commands basically don’t work
What exactly do you mean by project parameters? Are you talking about the specific project permissions, because if you are I do think for certain projects, certain project permissions differ. Sorry, I’m also confused on what you mean by:
Non-CLI knows what project it is based on path, but CLI does not
I mean so far, CLI can read my different permissions and what not. I do have a wider global projects permission system set up, but that is not aligned between the CLI and app. In general, I just right now where the permission configs live in the app versus where it lives for the CLI differ. Beyond that, for permissions for projects, it’s not exactly documented where these specific project permissions live and what not. I know I can just have AI can generate the permission commands and I can just manually copy and paste, however it would just be nice if there was a file I could just point the AI to handle this, for let’s say I’m setting up specific permissions for a project or a group of projects.
Thank you for digging into how the config files are structured! Here is how permission scopes work across the Antigravity App and Antigravity CLI (agy) per our Settings and Permissions documentation:
1. How the CLI merges all three scopes (/permissions): In the CLI, /permissions combines rules across three scopes—Global, Project, and Shared (Settings docs):
Shared (~/.gemini/config/config.json): Used by the Antigravity App (Settings → General → Global Permissions) and loaded by the CLI under the Shared scope. Editing ~/.gemini/config/config.json (or the Shared tab in /permissions) applies your rules to both the Desktop App and the CLI!
CLI Global (~/.gemini/antigravity-cli/settings.json): Loaded only by the CLI (Global tab in /permissions), which is why editing settings.json does not change the Desktop App.
Project (~/.gemini/config/projects/<project-id>.json): Project-scoped overrides (Project tab in /permissions).
2. Windows command matching (@Luckz): On Windows shells (PowerShell/cmd), commands that cannot be split into simple words require command(regex:git .*) (CLI command matching).