You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Antigravity: GOOGLE_APPLICATION_CREDENTIALS in provider env is saved but never reaches the runtime #30413
GOOGLE_APPLICATION_CREDENTIALS reaches the Antigravity runtime, so Vertex calls authenticate as the service account. Standalone agy honours the variable: AGY_ADC_AUTH=true GOOGLE_APPLICATION_CREDENTIALS=key.json agy -p "hi" works on the same machine.
If T3 deliberately strips the variable, the settings UI should say so instead of accepting and saving it.
Actual behavior
The value is saved (a provider-env-…-GOOGLE_APPLICATION_CREDENTIALS.bin secret appears at 19:33:52, and settings.json lists the entry). The runtime spawned at 19:34:55 has only AGY_ADC_AUTH=true and AGY_ACP_FORCE_FILE_STORAGE=1. GOOGLE_APPLICATION_CREDENTIALS is missing, so the runtime falls back to the user ADC file.
Why it matters: in Google Workspace orgs with Google Cloud session control, user ADC expires every N hours with invalid_grant "reauth related error (invalid_rapt)". A service-account key is the standard fix, and this route to it is silently blocked.
Workaround: overwrite ~/.config/gcloud/application_default_credentials.json with the service-account key. That works, but it changes ADC for every tool on the machine.
Activity