{"version":"2.1.301","anchor":"policy-limits-host-managed-env-bearer-path","canonical_anchor":"policy-limits-host-managed-env-bearer-path","heading":"Organization policy limits are checked when a host program manages sign-in","tier":"notice","area":"Policy Limits","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/policy-limits-host-managed-env-bearer-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Organization policy limits are checked when a host program manages sign-in\n\nWhen another program handles sign-in and only a token from an environment variable is in use, Claude Code now still fetches and re-checks policy limits\n\n**Unclear.** Which setups count as a host managing sign-in is not clear.\n\n**What**\n\nPolicy limits are restrictions an organization places on how Claude Code is used. Claude Code can be run by another program, the host, which takes care of signing in. In that case it may be given only a bearer token, a sign-in key, through an environment variable.\n\nIn this situation Claude Code now fetches the organization's policy limits, and fetches them again when needed. It also now tells apart three cases for that token:\n\n- The token has gone.\n\n- The token is the same as before.\n\n- The token has been replaced by a different one.\n\nBefore, it only checked yes or no.\n\n**Why**\n\nThis affects organizations that enforce policy limits on sessions run through the SDK or by another program that manages sign-in.\n\n- Area: Policy Limits\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: yes"}