Support hot-loading Chrome tools mid-session via /chrome
Resolved 💬 2 comments Opened Apr 7, 2026 by ieggel Closed May 20, 2026
Description
Running /chrome mid-session allows toggling the Chrome integration setting (enabled/disabled), but does not actually load the Chrome browser tools into the current session. The tools are only available if the session was started with claude --chrome or if "Enabled by default" was set before starting the session.
Expected behavior
Running /chrome and enabling Chrome integration should make Chrome browser tools available in the current session without requiring a full restart. This could be implemented as:
- Hot-loading the tools into the running session, or
- Automatically exiting and resuming the session with Chrome enabled (preserving conversation context)
Current behavior
/chromeopens a menu to manage permissions, reconnect extension, and toggle "Enabled by default"- Toggling the setting and reconnecting does not load Chrome tools into the running session
/contextstill shows no Chrome tools after enabling- User must exit and restart with
claude --chrometo get Chrome tools
Environment
- Claude Code v2.1.92
- Linux (Ubuntu)
- Chrome extension installed and detected (
Extension: Installed)
Workaround
Exit the session and restart with claude --chrome, or set "Enabled by default: Yes" so all future sessions include Chrome tools.
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗