{"version":"2.1.260","anchor":"new-bearer-token-verification-path-for-chrome-extension-poli","canonical_anchor":"new-bearer-token-verification-path-for-chrome-extension-poli","heading":"New bearer-token verification path for Chrome extension policy","tier":"internal","area":"Chrome & Browser","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/new-bearer-token-verification-path-for-chrome-extension-poli","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### New bearer-token verification path for Chrome extension policy\n\nChrome extension now verifies the bearer token against org policy to gate the bridge connection itself.\n\nClaude in Chrome gained functions to verify the current OAuth bearer token against the `allow_claude_browser_extension` policy, tracking denied\/unverified\/verified states to gate the browser bridge connection itself rather than just command availability.\n\n- Area: Chrome & Browser\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}