Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Device BridgeArea: what it touches
In DevelopmentKind: in v2.1.225,
In DevelopmentSection of the release
Both cloud attach and remote auth setup call startDeviceRegistration, which short-circuits unless tengu_violin_wood and the allow_remote_sessions policy permit.
What
Attaching a cloud session and completing remote auth setup both now attempt to bring up the device bridge for that session.
Details
both paths dynamically import startDeviceRegistration and call it with the session id, an access-token getter and the org uuid
registration short-circuits on its own enable and egress checks, so nothing happens unless tengu_violin_wood and the allow_remote_sessions policy both permit it
Evidence
startDeviceRegistration
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Read from
Names in the bundleallow_remote_sessions
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.225: not a boolean we can read
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.
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.
