Unclear Whether this behavior is active for this site's account is not established; the related gates are unread.
What
When Claude Code can't fetch your account's policy limits (usage/permission rules from your organization) and has no recent valid result to fall back on, it now recovers more aggressively:
- It arms a faster, randomized-timing retry instead of waiting for the normal poll interval
- It also watches for any other successful network call and immediately re-tries the policy-limits fetch when one happens (a "network kick")
- It now tracks how long it went without a valid result, and records that when a result is finally recovered
Why
This should shorten the window where Claude Code is operating without confirmed policy limits, particularly after a temporary network hiccup, by recovering as soon as the network shows signs of life again rather than waiting out a fixed timer.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Whether this behavior is active for this site's account is not established; the related gates are unread.