{"version":"2.1.285","anchor":"setup-vertex-command-hidden-when-a-managed-source-pins-it","canonical_anchor":"setup-vertex-command-hidden-when-a-managed-source-pins-it","heading":"\/setup-vertex is turned off when managed settings configure Vertex","tier":"notice","area":"Vertex","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/setup-vertex-command-hidden-when-a-managed-source-pins-it","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### \/setup-vertex is turned off when managed settings configure Vertex\n\nThe \/setup-vertex command is now unavailable when your organization's managed settings already provide a Vertex configuration\n\n**Unclear.** Exactly what the managed-settings check for Vertex looks at is not stated.\n\n**What**\n\n`\/setup-vertex` reconfigures Google Vertex AI authentication, project, region or model pins. It still stays hidden unless `CLAUDE_CODE_USE_VERTEX` is set. It now has a second condition: it is only enabled when managed settings (settings an administrator installs centrally) contain no Vertex entry.\n\n**Why**\n\nIn organizations that pin their Vertex setup through managed settings, the reconfigure command is no longer available, so users cannot change what the administrator set.\n\n- Area: Vertex\n- Names: `\/setup-vertex`, `CLAUDE_CODE_USE_VERTEX`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}