Organization policy limits are checked when a host program manages sign-in
When 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
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Policy LimitsArea: what it touches
ImprovementsKind: in v2.1.301,
ImprovementsSection of the release
Unclear Which setups count as a host managing sign-in is not clear.
What
Policy 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.
In 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:
The token has gone.
The token is the same as before.
The token has been replaced by a different one.
Before, it only checked yes or no.
Why
This affects organizations that enforce policy limits on sessions run through the SDK or by another program that manages sign-in.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhich setups count as a host managing sign-in is not clear.
