You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Device TrustArea: what it touches
In DevelopmentKind: in v2.1.239,
In DevelopmentSection of the release
What
Device enrollment records why it ran (proactive, device_bind, or after a server refusal) and whether the organisation required it. For consumer subscribers, and after a server refusal, it will enroll when the org merely allows the policy rather than enforcing it. A new path enrolls on demand just before binding a device session.
Details
Gated on tengu_violin_wood, which falls back to off, plus related gates and organisation policy.
The existing opt-out environment variable is still honoured.
Evidence
[trusted-device] Not enrolled, enrolling for a device-bound session
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Read from
Feature flag
tengu_violin_woodOff in both readings
The 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.239: off
Flag reading movedThe flag server now returns off for tengu_violin_wood, read as this 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.
Flag reading movedThe flag server now returns nothing at all, having stopped carrying it for tengu_violin_wood, read as this 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.
