The browser safety judge now sees where the tab actually navigated and judges against that.
What's wrong with this entry?
When Claude Code drives Chrome, the safety judge that reviews each browser action now receives a navigation record naming the page the tab moved from and to, and is told to treat it as fact: judge the action against the URL actually landed on, not the stated intent.
- The judge is instructed to treat form submissions, credential entry, code execution and data exposure on an unexpected origin as suspect.
- Always part of the Chrome judge prompt; no setting turns it off.
it is ground truth that the tab this action targets is on a different site
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.239
Chrome tabs opened by a session are closed when it ends
Both mention browser
-
v2.1.248
Browser-consent dialog defaults to declining
Both mention browser
-
v2.1.239
Clearer message when Claude in Chrome is not connected
Both mention browser