The cross-session remote-control bridge stays off unless the server enables it; its state shows in debug output.
Every bridge availability check reads one gate whose fallback is false.
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?
Every availability check for the cross-session remote-control bridge reads the same tengu_ccr_bridge gate, whose built-in fallback is false, so the bridge stays off unless the server turns the gate on. Its resolved value now appears in the CLI's internal debug output next to the rest of the feature-flag state.
- The same gate feeds a
remote_control_availabletelemetry field. - The debug line prints
unsetwhen no value has been resolved.
tengu_ccr_bridge=${String(o.tengu_ccr_bridge ?? "unset")}
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