Chrome auto-enable remains behind a flag whose fallback is off, with a context argument added to the check.
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.
tengu_chrome_auto_enable 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: off · compiled default in v2.1.238: off
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
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.