Title
Allow-listed commands in permissions.allow still trigger approval prompts, even with always-proceed and a trusted workspace
Device
Description
I don't know if this is an issue only I am facing.
Commands explicitly present in permissions.allow (via command(...) entries in settings.json) continue to trigger the "Run command?" approval prompt, even after:
- Adding exact-match entries for the commands in question
- Setting Tool Permission to
always-proceed via /config
- Confirming the workspace is listed under
trustedWorkspaces
- Fully restarting the CLI process (not just
/resume-ing a session)
- Validating that
settings.json is well-formed JSON
This matches a previously reported issue (google-gemini/gemini-cli or Antigravity forum thread: "Antigravity still asks permission even command is already on allowed list"), but persists after applying every suggested workaround from that thread.
Environment
- Antigravity CLI version:
<paste output of antigravity --version or /config>
- OS: Windows
<version> (PowerShell)
- Settings file path:
C:\Users\thakursaad\.gemini\antigravity-cli\settings.json
- Tool Permission mode:
always-proceed
enableTerminalSandbox: <true/false — check your settings.json>
Steps to reproduce
- Add a command to
permissions.allow in settings.json, e.g.:
"permissions": {
"allow": [
"command(Get-ChildItem)"
]
}
- Set Tool Permission to
always-proceed via /config.
- Confirm the current workspace is listed in
trustedWorkspaces.
- Fully close and restart the Antigravity CLI process.
- In a new session, prompt the agent to run the exact allow-listed command (e.g.,
Get-ChildItem).
Expected behavior
The command executes without an approval prompt, since it is present in permissions.allow and Tool Permission is set to always-proceed.
Actual behavior
The CLI still shows the "Run command?" approval prompt for the allow-listed command.
Additional notes
- This occurs even for commands added via the in-CLI "always allow" prompt option, not just hand-edited entries.
- Suspect this may relate to how
permissions.allow matching interacts with always-proceed mode specifically — i.e., the two mechanisms may not be talking to each other correctly, rather than a pure string-matching issue.
- Happy to share a redacted
settings.json or session transcript if useful for reproduction.
Title
Allow-listed commands in
permissions.allowstill trigger approval prompts, even withalways-proceedand a trusted workspaceDevice
Description
I don't know if this is an issue only I am facing.
Commands explicitly present in
permissions.allow(viacommand(...)entries insettings.json) continue to trigger the "Run command?" approval prompt, even after:always-proceedvia/configtrustedWorkspaces/resume-ing a session)settings.jsonis well-formed JSONThis matches a previously reported issue (google-gemini/gemini-cli or Antigravity forum thread: "Antigravity still asks permission even command is already on allowed list"), but persists after applying every suggested workaround from that thread.
Environment
<paste output of antigravity --version or /config><version>(PowerShell)C:\Users\thakursaad\.gemini\antigravity-cli\settings.jsonalways-proceedenableTerminalSandbox:<true/false — check your settings.json>Steps to reproduce
permissions.allowinsettings.json, e.g.:always-proceedvia/config.trustedWorkspaces.Get-ChildItem).Expected behavior
The command executes without an approval prompt, since it is present in
permissions.allowand Tool Permission is set toalways-proceed.Actual behavior
The CLI still shows the "Run command?" approval prompt for the allow-listed command.
Additional notes
permissions.allowmatching interacts withalways-proceedmode specifically — i.e., the two mechanisms may not be talking to each other correctly, rather than a pure string-matching issue.settings.jsonor session transcript if useful for reproduction.