You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Chrome & BrowserArea: what it touches
ImprovementsKind: in v2.1.285,
ImprovementsSection of the release
What
Claude in Chrome, which lets Claude control your Chrome browser, now runs a permission check before navigating or running a browser_batch call (one call that bundles several browser actions). The check works like this:
Addresses that are not ordinary web pages are refused.
Sites whose domain is on your deny list are refused.
Sites whose domain is on your allow list go ahead.
When the chromeClassifierFloorEnabled setting is on, Claude asks you before going ahead.
Input that cannot be read safely is refused with the message "Can't run this Claude in Chrome action: its input couldn't be safely checked."
For a browser_batch call, each action inside the batch is checked on its own.
Why
Browser navigation now follows per-domain permission rules, and a batch cannot slip an unchecked action past them.
Read from
Names in the bundlebrowser_batch
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is unclear whether this check replaces an earlier permission path for these actions or runs alongside it.
