{"version":"2.1.282","anchor":"websearch-on-vertex-and-the-vertexfoundry-beta-now-use-a-mo","canonical_anchor":"websearch-on-vertex-and-the-vertexfoundry-beta-now-use-a-mo","heading":"Which Vertex models get WebSearch is now decided by a model-version check","tier":"notice","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/websearch-on-vertex-and-the-vertexfoundry-beta-now-use-a-mo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Which Vertex models get WebSearch is now decided by a model-version check\n\nOn Vertex, WebSearch and a related beta header are now enabled by a single comparison against `claude-opus-4-0` instead of fixed model lists\n\n**Unclear.** Exactly which Vertex models the new check lets through is not known.\n\n**What**\n\nOn Google Vertex, two checks were rewritten: whether the WebSearch tool is available, and whether a beta request header is sent. Both now use one shared check against `claude-opus-4-0`. Before, WebSearch matched a fixed set of model-name patterns, and the beta header used a fixed list of model IDs.\n\n**Why**\n\nThe set of Vertex models that get WebSearch and the beta header may be different from before, possibly including models that were not on the old lists.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}