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
Event uploads for remote sessions now send a trusted-device token, and when the server refuses with a 403 for an untrusted device the client can re-enroll and try again rather than dropping the events. Telemetry separates this case from an ordinary success.
Details
Parsing the refusal body is behind the tengu_violin_wood gate, which falls back to off, so on a stock build the retry path does not engage.
Evidence
remote_send_event_untrusted_device
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.
