{"version":"2.1.319","anchor":"claude-in-chrome-secret-fill-vs-page-code-mutual-exclusion","canonical_anchor":"claude-in-chrome-secret-fill-vs-page-code-mutual-exclusion","heading":"Claude in Chrome keeps secret-filling and page code apart","tier":"notice","area":"Claude in Chrome","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/claude-in-chrome-secret-fill-vs-page-code-mutual-exclusion","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Claude in Chrome keeps secret-filling and page code apart\n\nClaude in Chrome now refuses to mix secret-filling with running code in a page in one session, and rejects nested or unknown batch actions\n\n**What**\n\nClaude in Chrome, which lets Claude control your Chrome browser, now applies more checks:\n\n- Fill tools, which put secrets such as passwords into a page, are refused once code has run in a page in the same session, and the reverse is refused too.\n\n- A `browser_batch` call (one call bundling several browser actions) is rejected if it contains another `browser_batch` or an action it does not recognise.\n\n- Calls that need a permission check are refused when Claude Code cannot confirm which browser the tab belongs to.\n\n- The check that the browser's helper program is still running gets a second try when the connection is relayed.\n\nThe first rule applies only where secret-filling tools are available.\n\n**Why**\n\nThese rules stop code in a page from reaching a secret Claude has filled in. Sequences of actions that used to work may now be refused.\n\n- Area: Claude in Chrome\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}