{"version":"2.1.319","anchor":"gateway-login-notice-support","canonical_anchor":"gateway-sign-in-screen-login-notice-extension","heading":"Gateway sign-in screen can show a login notice and host name","tier":"use","area":"LLM Gateway","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/gateway-login-notice-support","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Gateway sign-in screen can show a login notice and host name\n\nEnterprise gateways can send a login_notice of up to 500 characters, shown with the host name on Claude Code's device sign-in screen\n\n**What**\n\nSome organisations sign in to Claude Code through their own gateway, using a device code you enter in a browser. That flow gains an optional message:\n\n- The gateway's device-authorization response may include `login_notice`, a string of at most 500 characters. The gateway config schema gains a matching `login_notice` field.\n\n- Claude Code reads it and passes it to the sign-in screen as `loginNotice`. The protocol document says the client shows it next to the code.\n\n- The polling screen now also shows the host name taken from the URL. Before, it showed only the user code and the verification address.\n\n- The OIDC config validator warns that `login_notice` has no effect in CRI-only deployments, because no one can sign in there and so no one sees it.\n\n**Why**\n\nGateway operators can show an organisation-specific message at sign-in, and you can see which host you are signing in to.\n\n- Area: LLM Gateway\n- Names: `login_notice`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}