"Agent Non-Workspace File Access" needed for the agent to work with project files

Google Antigravity
1

Using this forum because even “Provide Feedback” is broken in Antigravity version 1.23.2.

A recent update has broken something in the way the agents sees a “workspace”:
I now have to grant “Agent Non-Workspace File Access” in order for the agent to work with project files. This was not necessary before.
Here is what a Gemini 3.1 Pro agent had to say about the problem:

I ran the pwd command, and it shows that I am currently restricted to my local scratch directory: C:\Users\staticnoiselog\.gemini\antigravity\scratch Due to the inconsistent workspace mapping caused by the update, my access to your project directories (C:\Users\staticnoiselog\IdeaProjects\order-sleuth and C:\Users\staticnoiselog\IdeaProjects\ai-toolbelt) is currently blocked by workspace validation. Before we can continue with the Requirements Engineering Playbook and start drafting the new requirements, we need to restore my access. Could you please either: Turn off workspace validation in your settings, OR Re-add order-sleuth and ai-toolbelt as active workspaces in your IDE?

I tried everything I could think of to “re-add” the projects to the active workspace (although the files obviously were part of the current workspace).
Nothing helped. So I am forced now to give Antigravity full access to everything on my computer by granting “Agent Non-Workspace File Access”. A massive security risk that is not acceptable.
By the way: In one conversation with the agent it finally decided to internally work around the limitation, even with “Agent Non-Workspace File Access” DISABLED. So this new security harness that just causes issues is not even working properly.

It also remains unclear what exactly a “workspace” is for Antigravity agents. If it is not strictly the same thing that VisualStudio Code names “workspace”, I strongly suggest using a different name. Otherwise the concepts are mixed up and are super confusing for users.

=======================================

REPRODUCING:

Use Windows 11, install Git Bash.

Use these versions:
Antigravity Version: 1.23.2
VSCode OSS Version: 1.107.0 (user setup)
Commit: 15487b3041e65228cae24980a3f796c905ef582c
Date: 2026-04-16T08:28:19.366Z (4 wks ago)
Electron: 39.2.3
Chromium: 142.0.7444.175
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26100
Language Server CL: 900566399

Configure these user settings in Antigravity:

{
“workbench.colorTheme”: “Default Light Modern”,
“files.eol”: “\n”,
“terminal.integrated.defaultProfile.windows”: “Git Bash”,
“terminal.integrated.env.windows”: {
“CHERE_INVOKING”: “1”,
“BASH_ENV”: “~/.bash_profile”
},
“terminal.integrated.cwd”: “${workspaceFolder}”,
“terminal.integrated.enableVisualBell”: true,
“kotlinLSP.jdkForSymbolResolution”: “C:\Users\staticnoiselog\.gradle\jdks\eclipse_adoptium-25-amd64-windows.2”,
“kotlinLSP.jrePathToRunLsp”: “C:\Users\staticnoiselog\.gradle\jdks\eclipse_adoptium-21-amd64-windows.2”
}

Use “File, Open Folder…” to open an initialized Git project (contains .git folder).

Ask the agent Gemini 3.1 Pro (High) to issue a “pwd” and see if it can access the project files.