Antigravity CLI workspace permission vs. .env permission

Google Antigravity
1

Antigravity CLI grants the workspace read and write access, but also sets read_file(.env) to “ask” and write_file(.env) to “ask”. However, Gemini assumes .env is within the workspace and reads it directly without requesting permission.

expected results:
Even if the workspace has full access, .env read/write permission should still be requested.

2

Hi @xfox, Welcome to the Forum!

We tried reproducing this behavior in our testing, but the agent consistently requested permission before accessing the .env file on our end.

If you are still experiencing this, please share a few details to help us investigate further:

  • CLI Version: Your specific Antigravity CLI version?
  • Model: The model you were using when this occurred?
  • Operating System: Your operating system and version?
  • Workspace Permissions: Any configured workspace permission settings (e.g., read/write, “always allow”)?
3

Hi,
I’ve simplified the environment. I hope this helps you replicate the issue.

Antigravity CLI 1.1.1
Model Gemini 3.5 Flash (High)
OS win10 22H2, run agy under cygwin
permissions:
 Read & Write Access:  C:\software\antigravity_project\test_env   
 Always Prompts for Permission ( ask ):
   Any file edits or reads in .env , .env.* , .npmrc , .pypirc , .netrc , .git-credentials , .vscode , .cache , .git

/cygdrive/c/software/antigravity_project/test_env
$ more test.py 
from dotenv import load_dotenv
import os

load_dotenv()
var = os.getenv("HAHAHA")
print(var)

$ more .env 
YOU CANT READ THIS lol

圖片
圖片1094×598 51.8 KB