{"version":"2.1.323","anchor":"built-in-plugin-source-for-gateway-model-id-warnings","canonical_anchor":"built-in-plugin-source-for-gateway-model-id-warnings","heading":"Gateway checks warn about model IDs Claude Code does not recognise","tier":"notice","area":"Elsewhere","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/built-in-plugin-source-for-gateway-model-id-warnings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Gateway checks warn about model IDs Claude Code does not recognise\n\nWhen a sign-in gateway offers model IDs Claude Code does not know, its diagnostics now say to list them in `modelPicker.options`\n\n**What**\n\nSome organisations route Claude Code through a gateway, a server in between that handles sign-in (here, sign-in through OIDC, a common single sign-on standard) and passes requests on. Claude Code's gateway diagnostics now warn when such a gateway offers model IDs that Claude Code does not recognise.\n\nThe warning says to list those models in `modelPicker.options`, the setting that controls which models the `\/model` picker shows, and gives an example that uses `behavesAs` to say which known model each one acts like.\n\n**Why**\n\nAdmins running their own model gateway get a pointer to how to make unfamiliar models show up and behave properly, instead of being left with models Claude Code does not know what to do with.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}