What it is
Local policy-limits cache now tracks which account is logged in and reacts to account switches
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.271.
Presence across releases
0The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.
First cited
1The earliest release whose published evidence quoted tengu_policy_limits_principal_changed was v2.1.271, 14 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table above.
Gate readings
0No release here has a gate table behind it for this flag. Most published releases have none at all: the readings exist only for versions the pipeline captured flag state on.
Names beside it
Every feature flag in the inventory starting tengu_policy_limits, up to twelve of them.
tengu_policy_limits_cache_state_at_first_promptThree new telemetry events added for refusal-fallback prompts and policy-limits checks never mined
tengu_policy_limits_fetchPolicy limit fetch events now record how you authenticated and why the server said no. never mined
tengu_policy_limits_late_compositionBilling, artifact, MCP and subagent call sites also take credentials explicitly now. never mined
tengu_policy_limits_verdict_recoveredClaude Code now retries faster and recovers sooner when it can't fetch your policy limits never mined
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the feature flag does. All feature flags.