Group of 2 You'll notice Notable
No documentation found
GCP credential checks now distinguish timeout from failure and honor a new project env var fallback.
The GCP ADC pre-check used before deciding whether to run the configured gcpAuthRefresh command (Yfr()) previously returned only true/false; it now returns 'valid', 'timeout', or 'invalid', logging distinct warning messages for a timeout versus an outright failure.
It also now passes an explicit projectId into the GoogleAuth client construction, sourced from existing variables like GCLOUD_PROJECT or the new fallback ANTHROPIC_GOOGLE_CLOUD_PROJECT.
Names in the bundleANTHROPIC_GOOGLE_CLOUD_PROJECT
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agree
Fixed gcpAuthRefresh opening a browser at startup when the Google credential check was slow, even though the credential was still valid