{"version":"2.1.268","anchor":"chrome-bridge-bridge-received-debug-logging-now-gated-behi","canonical_anchor":"chrome-bridge-bridge-received-debug-logging-now-gated-behi","heading":"Chrome bridge \"Bridge received\" debug logging now gated behind isDebugEnabled","tier":"internal","area":"Chrome & Browser","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/chrome-bridge-bridge-received-debug-logging-now-gated-behi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Chrome bridge \"Bridge received\" debug logging now gated behind isDebugEnabled\n\nChrome bridge's verbose \"Bridge received\" debug log now only prints when debug mode is actually enabled\n\n**What**\n\nWhen Claude in Chrome's bridge receives a message it doesn't recognize, it used to always log the full payload (`Bridge received: ...`) for debugging. Now this logging only happens if debug mode is enabled; if there's no way to check, it defaults to still logging.\n\n**Why**\n\nThis avoids dumping potentially large or sensitive message payloads to logs during normal use, restricting the verbose output to when debugging is actually turned on.\n\n- Area: Chrome & Browser\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}