Bridge worker sessions record which account launched them, but the bridge is off.
Owner stamping for bridge children is wired but unreachable while the bridge stays off.
tengu_ccr_bridge On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.251: on
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
What's wrong with this entry?
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.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Remote bridge replaces stale-epoch recovery with a one-shot supersession close
Both mention bridge
-
v2.1.236
Remote bridge waits for the disconnect notice, and an inbox fetch that is always off
Both mention bridge
-
v2.1.236
Bridge shuts down cleanly on SIGHUP
Both mention bridge