claude-in-chrome: --chrome flag lost on session resume + duplicate bot auto-closes without resolution

Bug 1: --chrome flag doesn't persist on session resume

Steps to reproduce

1. Start Claude Code with claude --chrome
2. Confirm chrome MCP tools are registered (they appear as deferred tools)
3. Exit session with /exit
4. Resume the session
5. --chrome flag is gone — ps aux | grep claude shows no --chrome
6. All claude-in-chrome MCP calls fail with "Browser extension is not connected"

Expected

Resuming a session started with --chrome should preserve the flag and reinitialize the MCP server.

Actual

The flag is silently dropped. The only workaround is to never resume — always start a fresh session with claude --chrome.

---

Bug 2: claude-in-chrome connection fails even with correct setup

Environment

• Claude Code 2.1.101, macOS Darwin 23.6.0
• Chrome 147.0.7727.55
• "Claude in Chrome (Beta)" extension installed and enabled
• Same account on CLI and Chrome (hanjoon.choe@bespinglobal.com, Team plan)
• CLI launched with claude --chrome

What was tried (all failed)

• Extension installed, enabled, account verified ✓
• chrome://inspect/#remote-debugging toggled ON — stuck at "starting..."
• --remote-debugging-port=9222 CLI flag — Chrome 147 macOS ignores it (port never binds)
• Full Chrome kill + relaunch with flag — same result
• Claude Code restart after extension install — same error

Result

Every call returns: "Browser extension is not connected"

This appears to be the same issue as #37833 (bridge WebSocket auth failure) but that issue was also auto-closed without resolution.

---

Feedback: duplicate bot is counterproductive

Issue #46658 was auto-tagged as duplicate of #37833, #45227, #40758. None of those issues have an official response or resolution. The bot pattern-matches titles and auto-closes in 3 days.

This means:

• Real bugs get buried without anyone looking at them
• Users who took the time to file detailed repro steps get their issues silently closed
• There's no way to tell if this is a known issue being worked on or just ignored

Suggestion: If a feature is in Beta and has recurring connection issues, a pinned issue or FAQ would be more useful than auto-closing every report.