{"version":"2.1.296","anchor":"remote-settings-gateway-warnings-distinguish-code-tab-rules","canonical_anchor":"remote-settings-gateway-warnings-distinguish-code-tab-rules","heading":"Fewer settings warnings for gateways that report no Code tab rules","tier":"notice","area":"Gateway","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/remote-settings-gateway-warnings-distinguish-code-tab-rules","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Fewer settings warnings for gateways that report no Code tab rules\n\nClaude Code no longer warns about a gateway when it reports no Code tab rules, and says when the check could not be made\n\n**What**\n\nA gateway is a server that sits between Claude Code and the API. When a gateway is not an accepted source of settings, Claude Code used to always show a warning. It now first asks the gateway whether it has Code tab rules for you:\n\n- If the gateway says it has none, no warning is shown and the event is only recorded.\n\n- If Claude Code could not ask the gateway, the warning says so and suggests trying again.\n\n- When the result could not be settled, the message now says it could not be checked.\n\n**Why**\n\nIf you use a gateway that has no rules for you, you get fewer warnings that do not apply. When the check fails, the message now tells you so and suggests retrying.\n\n- Area: Gateway\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}