In-app Browser drives installed Google Chrome and quits my everyday Chrome session (regression ~Jul 21-22)

Environment

• Claude Desktop app (macOS, Darwin 25.3.0, Apple Silicon)
• Claude Code CLI 2.1.79
• Google Chrome 150.0.7871.129

What happens
Since ~Jul 21–22, whenever Claude uses the in-app Browser, my everyday Google Chrome session is shut down. I can't browse and use Claude at the same time.

Root cause (from local inspection)
The in-app Browser doesn't use a bundled/isolated browser — it launches my installed Chrome:

/Applications/Google Chrome.app/.../Google Chrome --headless=new --remote-debugging-port=9351 --user-data-dir=/tmp/chrome-v2

Claude.app bundles no Chromium of its own. It uses a separate profile (/tmp/chrome-v2) but the SAME app bundle as my daily Chrome, so launching/tearing down the automation instance takes down my running session. The chrome-v2 naming + timing suggests a recent switch to a new browser implementation.

Expected
Automation should use an isolated/bundled browser, OR expose a setting to point it at a separate binary (I have Chrome for Testing installed and ready).

Impact
Can't browse in Chrome while Claude works — have to switch to Safari/Arc as a workaround.