{"version":"2.1.319","anchor":"chrome-bridge-calls-can-target-a-specific-browser-and-wait-f","canonical_anchor":"chrome-bridge-calls-can-target-a-specific-browser-and-wait-f","heading":"Browser actions can be aimed at one specific Chrome browser","tier":"notice","area":"Claude in Chrome","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/chrome-bridge-calls-can-target-a-specific-browser-and-wait-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Browser actions can be aimed at one specific Chrome browser\n\nBrowser tool calls can now target a particular browser and are refused if that browser is no longer selected or disappears\n\n**What**\n\nBefore, Claude Code sent browser actions to whichever single browser was selected. A browser action can now be aimed at a specific browser and given its own time limit. With that:\n\n- A call is refused with \"its browser is no longer selected\" if the selected browser changed in the meantime.\n\n- A targeted call is rejected if its browser disappears.\n\n- A targeted call cannot raise a permission prompt, the question asking you to approve an action.\n\n- When looking for browsers again, Claude Code waits for the previously selected browser extension to come back before picking one.\n\n**Why**\n\nWhen more than one browser is connected, actions are less likely to land in the wrong browser or jump to another one after a brief disconnect.\n\n- Area: Claude in Chrome\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}