Automatic Chrome integration stays disabled; only its decision function changed shape.
Chrome auto-enable remains behind a flag whose fallback is off, with a context argument added to the check.
tengu_chrome_auto_enable 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: off · compiled default in v2.1.238: on
Read once, for one account on one subscription tier, against v2.1.238. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Automatically enabling the Chrome integration is still behind tengu_chrome_auto_enable, whose fallback is off, so it stays disabled absent a server value; the decision function now takes a context argument.
- Successful bridge connections now record whether the connection was
pairedorwaiting. - The availability funnel flag is passed through when resolving Chrome bindings.
chrome_bridge_connection_succeeded
Strings lifted out of the shipped bundle, so the claim above can be checked against them.