The policy-limits fetch/save pipeline now tracks a sessionGeneration per fetch and compares it before applying results, so a fetch or cache write that outlives an account switch is discarded instead of being applied to the new account's session. Look for new log lines "Policy limits: skipped saving a fetch that outlived the account session" and "Policy limits: Discarding a fetch that outlived the account session".
It also handles a 304 response with no outstanding ETag by falling back to stale cache, logging "Policy limits: 304 with no outstanding ETag — using stale cache", and merges/dedupes compliance_taints across cache and server responses so entries aren't lost, logging "Policy limits: lossy cached compliance_taints — kept the session taint set" when that happens.
tengu_rustling_orbit Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.261: off
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.261. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.