When creating a device-bound session, Claude Code can now ask the server for an 'elevated' security tier as part of an 'ask' proof-header flow. If the server rejects that elevated request with a 4xx error, the client logs the reason and retries the same bound-session creation without asking for elevation. A new telemetry event, cloud_elevated_create, records whether the elevation request was honored, unsupported, or refused, distinguishing reasons like an untrusted device or an unavailable device check.
This lets Claude Code opportunistically request a stronger security tier for a device-bound session while still falling back gracefully and completing the session setup if the server can't or won't grant it.
Gate state
No sentence about tengu_breezy_fairy on/off for this release; the finding notes it read off for this site's account and off for the anonymous baseline, with no reading taken under this release yet.
tengu_breezy_fairy 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.274: 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.274. 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.
New in this build: tengu_breezy_fairy