{"version":"2.1.304","anchor":"gateway-bootstrap-response-now-carries-oauthbearersha256-and","canonical_anchor":"gateway-bootstrap-response-now-carries-oauthbearersha256-and","heading":"Gateway model discovery records more about its startup replies","tier":"internal","area":"Models","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/gateway-bootstrap-response-now-carries-oauthbearersha256-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Gateway model discovery records more about its startup replies\n\nStartup replies used by gateway model discovery now carry two more details, and a reply for skipped discovery is fixed\n\n**What**\n\nGateway model discovery is turned on with `CLAUDE_CODE_ENABLE_GATEWAY_MODEL_DISCOVERY`. A gateway is a server that sits between Claude Code and the model. The replies Claude Code receives when it starts this process now carry two more details:\n\n- a fingerprint of the sign-in token it used\n\n- whether the server address had moved when the request was sent\n\nThe check of whether an organisation can use it also gained a new filter value. A reply returned when discovery is skipped now refers to the right value.\n\n**Why**\n\nThese are internal changes to how gateway discovery works.\n\n- Area: Models\n- Names: `CLAUDE_CODE_ENABLE_GATEWAY_MODEL_DISCOVERY`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}