{"version":"2.1.285","anchor":"vertex-model-accessibility-probing-and-memory","canonical_anchor":"vertex-model-accessibility-probing-and-memory","heading":"Vertex model availability checks reworked","tier":"notice","area":"Vertex","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/vertex-model-accessibility-probing-and-memory","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Vertex model availability checks reworked\n\nClaude Code's check of which Vertex models your account can use was rebuilt: the old cached check is gone and a new one remembers refused models\n\n**Unclear.** It is not clear what starts the test, whether it is switched on for everyone, or whether it leads to Claude Code switching models on its own.\n\n**What**\n\nWhen you use Claude on Google Vertex, Claude Code checks whether your account can reach the models it wants to use. This check is called a probe.\n\n- The old probe function, which cached results and logged lines like `[vertex-probe] ...: accessible (cached)`, has been removed.\n\n- New functions probe whether the default and fallback models are accessible. They remember the results, record models that were refused, and log `[3p-model-memory] vertex record failed` when saving a result fails.\n\n- Results are keyed on `ANTHROPIC_VERTEX_PROJECT_ID`, `ANTHROPIC_GOOGLE_CLOUD_PROJECT`, `ANTHROPIC_VERTEX_BASE_URL`, `GOOGLE_APPLICATION_CREDENTIALS`, `CLOUDSDK_CONFIG` and `CLAUDE_CODE_SKIP_VERTEX_AUTH`, so changing any of them triggers a fresh check.\n\n**Why**\n\nOn Vertex, Claude Code now remembers which models your account cannot use and checks the fallback model too. This can lead to an automatic switch to another model when one is not available. Changing your project, endpoint or credentials starts the check over.\n\n- Area: Vertex\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}