{"version":"2.1.310","anchor":"gcp-credential-check-passes-clientoptions","canonical_anchor":"gcp-credential-check-passes-clientoptions","heading":"Google Cloud credential check now passes client options to Google's sign-in library","tier":"internal","area":"Elsewhere","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/gcp-credential-check-passes-clientoptions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Google Cloud credential check now passes client options to Google's sign-in library\n\nWhen Claude Code checks your Google Cloud credentials, it now hands a set of client options to Google's authentication library\n\n**Unclear.** It is not clear which options are passed, so it is unclear whether this changes proxy or certificate handling for the credential check.\n\n**What**\n\nWhen you use Claude Code through Google Cloud (Vertex AI), it first checks that your Google Cloud credentials work. That check uses Google's own authentication library, called `GoogleAuth`. Claude Code now passes a set of client options (settings that control how that library makes its network connections) into `GoogleAuth` during the check. Before, it passed none. The check still reports \"GCP credentials check timed out\" if it takes too long.\n\n**Why**\n\nThis may change how the credential check connects to Google, for example whether it follows the same network setup as the rest of Claude Code. If the check behaved differently for you before, it is worth trying again on this build.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}