{"version":"2.1.238","anchor":"chrome-auto-enable-remains-off-pairing-state-now-recorded","canonical_anchor":"chrome-auto-enable-remains-off-pairing-state-now-recorded","heading":"Chrome auto-enable remains off; pairing state now recorded","tier":"soon","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/chrome-auto-enable-remains-off-pairing-state-now-recorded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Chrome auto-enable remains off; pairing state now recorded\n\nAutomatic Chrome integration stays disabled; only its decision function changed shape.\n\n**What**\n\nAutomatically 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.\n\n**Details**\n\n- Successful bridge connections now record whether the connection was `paired` or `waiting`.\n- The availability funnel flag is passed through when resolving Chrome bindings.\n\n**Evidence**\n\n`chrome_bridge_connection_succeeded`\n\n- Flag `tengu_chrome_auto_enable`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.238; this account: on, anonymous baseline: off, compiled default: off)\n- Area: Elsewhere\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}