The bridge is the connection Claude Code uses to link this machine with sessions running elsewhere. When Claude Code registers the machine over the bridge, it can now say whether cloud sessions may use this machine as a tool host, meaning a place where their tools run. Before, this part of the code was switched off entirely and nothing was sent.
- When Claude Code decides to offer the machine, it sends a tool host marker together with its version and platform.
- When it decides to withdraw the offer while reusing an existing registration, it sends empty values to clear the earlier ones.
The debug log records the decision as "cloud sessions may use this folder: yes", or "no" followed by what blocked it. Part of the decision depends on a server-controlled setting, tengu_radiant_heron, which is off unless it is switched on remotely.
This connects the path that lets cloud sessions use a folder and its tools on your own machine through the bridge. Until now that path was not built into Claude Code at all.
tengu_radiant_heron 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.283: 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.283. It isn't a statement about your account. What a flag value here can and cannot tell you
The other conditions in the decision, such as platform, a local device setting and policy, are not fully known.
New in this build: tengu_radiant_heron