[Bug] Claude Code Chrome extension incompatible with Chrome Dev/Beta/Canary release channels

Bug Description
Claude in Chrome does not work when the extension is installed in Google Chrome Dev (or Beta/Canary) instead of Chrome stable. macOS, Claude Code 2.1.228. Two separate hardcoded browser lists omit the Chrome release channels. (1) claude --chrome writes com.anthropic.claude_code_browser_extension.json only to ~/Library/Application Support/Google/Chrome/NativeMessagingHosts/ and never to the Chrome Dev directory, so the extension can never connect. Symlinking that manifest into the Chrome Dev NativeMessagingHosts directory fixes it completely: the bridge connects and all 22 tools work. (2) After that fix, /chrome still reports "Extension: Not detected" forever, because the detection scan iterates a hardcoded list [chrome, brave, arc, edge, chromium, vivaldi, opera] where chrome maps to Library/Application Support/Google/Chrome, so it never looks inside Chrome Dev. This also permanently greys out "Manage permissions" and "Reconnect extension". Note the session-startup banner DOES detect the extension correctly, so the two code paths disagree. (3) Minor: /chrome > "Install Chrome extension" only opens the Web Store link and does not write the manifest; only claude --chrome does, which makes that menu item a dead end when the extension is already installed. Please add Chrome Dev/Beta/Canary to both the manifest write path and the extension detection path.

Environment Info

• Platform: darwin
• Terminal: tmux
• Version: 2.1.228
• Feedback ID: 59e25564-56db-4b2f-9163-ae5d43932fff

Errors

[]