{"version":"2.1.285","anchor":"tengu-joyful-parasol-makes-the-chrome-setting-consent-gated","canonical_anchor":"tengu-joyful-parasol-makes-the-chrome-setting-consent-gated","heading":"The Claude in Chrome setting is now marked as needing consent","tier":"notice","area":"Chrome & Browser","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/tengu-joyful-parasol-makes-the-chrome-setting-consent-gated","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### The Claude in Chrome setting is now marked as needing consent\n\nThe 'Claude in Chrome enabled by default' setting is now flagged as needing consent, and a new message says some features are limited by policy\n\n**Unclear.** It is not clear what the consent flag changes in the settings panel or whether it is tied to the organization policy message.\n\n**What**\n\nIn the settings panel, the row labelled 'Claude in Chrome enabled by default' is now flagged as needing consent. Several other rows carry the same flag, and the panel checks it in several places. This flag is controlled by a server-side switch, and when the server sends nothing, the row is flagged.\n\nThe build also includes a new message: 'Per your organization's policy, some features are limited'.\n\n**Why**\n\nThe settings panel now treats this setting differently from before. You may see the Chrome setting behave differently there, or see the policy message.\n\n- Flag `tengu_joyful_parasol`: Not enough to say (read for one account on one subscription tier against v2.1.285; this account: no value returned, anonymous baseline: no value returned, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Chrome & Browser\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}