Owner stamping for bridge children is wired but unreachable while the bridge stays off.
A session spawned as a bridge worker now has the launching account and organization identifiers stamped into its environment by the supervisor, and reads them back at startup to record who owns it. The bridge feature itself is off in this build, so nothing reaches this path by default.
- only applies to workers whose environment kind is
bridge - the whole bridge feature is gated on
tengu_ccr_bridge, which defaults to off
CLAUDE_CODE_BRIDGE_OWNER_ACCOUNT_UUID: te?.accountUuid
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_ccr_bridge Off by default, switched on for this accountThe shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.
This account: on · anonymous baseline: on · compiled default in v2.1.251: off
Read once, for one account on one subscription tier, against v2.1.251. 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.
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.