Bug: Allow List Terminal Commands entries are moved to Terminal Commands after IDE restart

Hello,

I am reporting a persistence/configuration bug in Antigravity IDE.

Environment:

  • Antigravity IDE: 2.5.5
  • VSCode OSS: 1.107.0 (user setup)
  • Commit: ecfbad74d93962fc8ca485d93ab9b4f3d4c…
  • Electron: 39.2.3
  • OS: Windows 11 x64, build 10.0.26200
  • Shell: PowerShell

Expected behavior:
When “Terminal Command Auto Execution” is set to “Request Review”,
a command added under:

Advanced > Allow List Terminal Commands

should remain in that list after restarting the IDE. It should then
run without a confirmation prompt, while commands outside the allowlist
should still require review.

Actual behavior:
After restarting the IDE, every command added to:

Advanced > Allow List Terminal Commands

is removed from that section and appears instead under:

Advanced Command Access > Terminal Commands

The command is then no longer auto-approved. For example, after adding
“git diff” to the allowlist, restarting the IDE, and asking the agent
to execute “git diff”, Antigravity asks for permission.

Minimal reproduction:

  1. Open Settings > General.
  2. Set “Terminal Command Auto Execution” to “Request Review”.
  3. Under Advanced > Allow List Terminal Commands, add:
    git diff
  4. Confirm that “git diff” appears in the allowlist.
  5. Restart Antigravity IDE.
  6. Open Settings > General again.
  7. Observe that “git diff” has been removed from the allowlist and is now
    listed under Advanced Command Access > Terminal Commands.
  8. Start a new agent message and ask it to run:
    git diff
  9. The agent requests approval.

Impact:
It is not possible to persistently use the intended security model:
“ask by default, auto-allow only a narrow set of safe commands”.

I can provide screenshots showing the state before and after restart.

I tested with a new agent message after changing the setting, so this does not appear to be caused by the documented behavior that policy changes apply only to new messages.

I am experiencing the exact same issue.

A further complication is that Allow List Terminal Commands (and Deny List) likely uses partial matching—meaning ls would also cover ls -la—whereas Terminal Commands relies on exact matching, so the latter case is not covered.

Please fix this by either resolving the bug or unifying the behavior so that both use partial matching (or regular expressions).