{"version":"2.1.261","anchor":"gcp-credentials-check-now-reports-why-it-failed","canonical_anchor":"gcp-credential-check-becomes-tri-state-and-honors-anthropic","heading":"GCP credential check reports failure reason and honors ANTHROPIC_GOOGLE_CLOUD_PROJECT","tier":"notice","area":"Cloud Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261\/e\/gcp-credentials-check-now-reports-why-it-failed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261","markdown":"### GCP credential check reports failure reason and honors ANTHROPIC_GOOGLE_CLOUD_PROJECT\n\nGCP credential checks now report why they failed instead of just pass\/fail.\n\nThe 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.\n\nIt 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`.\n\n- Area: Cloud Auth\n- Names: `ANTHROPIC_GOOGLE_CLOUD_PROJECT`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}