[BUG] --chrome flag doesn't auto-connect, requires manual /chrome every session

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Starting claude --chrome doesn't actually connect to Chrome. The browser tools don't work until I manually run /chrome to establish the connection. This happens every single session.

What Should Happen?

I'd expect --chrome to handle the connection automatically so I can just start using browser tools right away. Instead I have to remember to reconnect manually each time, which also makes non-interactive mode (-p) completely unusable with Chrome.

Error Messages/Logs

Steps to Reproduce

1. Run claude --chrome
2. Try any browser tool - it fails because there's no connection
3. Run /chrome and reconnect manually
4. Now it works

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.1

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

Terminal Emulator: Kitty