Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.319 ·

Claude in Chrome keeps secret-filling and page code apart

Claude in Chrome now refuses to mix secret-filling with running code in a page in one session, and rejects nested or unknown batch actions

You'll notice Improvements
JSON All of v2.1.319
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Claude in ChromeArea: what it touches
ImprovementsKind: in v2.1.319,
ImprovementsSection of the release
What

Claude in Chrome, which lets Claude control your Chrome browser, now applies more checks:

  • 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.
  • 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.
  • Calls that need a permission check are refused when Claude Code cannot confirm which browser the tab belongs to.
  • The check that the browser's helper program is still running gets a second try when the connection is relayed.

The first rule applies only where secret-filling tools are available.

Why

These 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.

See this entry in the whole of v2.1.319 →

Feedback