{"version":"2.1.321","anchor":"rate-limit-status-handling-skipped-for-gateway-or-auth-token","canonical_anchor":"rate-limit-status-handling-skipped-for-gateway-or-auth-token","heading":"Gateway and auth-token setups now run the usage check and skip one usage-limit record","tier":"notice","area":"Gateways","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/rate-limit-status-handling-skipped-for-gateway-or-auth-token","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Gateway and auth-token setups now run the usage check and skip one usage-limit record\n\nSessions through a gateway, or with a custom base URL and `ANTHROPIC_AUTH_TOKEN`, now get the usage check and skip the usage-limit status record\n\n**What**\n\nClaude Code now treats a session as running through a gateway, a service that sits between Claude Code and the model, in either of these cases:\n\n- the provider is set to `gateway`\n\n- a custom base URL, the address Claude Code sends its requests to, is set together with `ANTHROPIC_AUTH_TOKEN`\n\nFor these sessions, Claude Code no longer makes the record it usually makes when your claude.ai usage-limit status changes. The check of how much usage you have left now also runs for them.\n\n**Why**\n\nIf you use a gateway or your own auth token, how Claude Code tracks your usage limits is now different from a normal claude.ai sign-in.\n\n- Area: Gateways\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}