[FEATURE] Option to hide the 'Browser connected' banner in VS Code; × currently disconnects instead of dismissing

Status Open
Reported on v2.1.289
Maintainer reply None cached
Activity 1 comment · opened Oct 4, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

In the VS Code extension, when Claude in Chrome is set to Enabled by default, every new session shows a "Browser connected" banner above the prompt box. It stays there for the whole session.

I want Chrome connected by default. I don't need a permanent reminder that it is.

The only control on the banner is an ×, which looks like "dismiss" but actually disconnects the browser. Its tooltip says "Disconnect browser" and it calls disableChromeMcp(). So the natural way to tidy the banner away silently turns off the feature I enabled. Nothing in the UI warns about this before you click.

Proposed Solution

Either of these would solve it:

  1. A setting to hide the banner while connected. For example claudeCode.showBrowserConnectedBanner: false, or a "Show connection banner" toggle under /chrome. Keep showing the banner for connecting and error, since those need attention.
  2. Separate "dismiss" from "disconnect". Make × hide the banner (and remember that per user). Put "Disconnect" somewhere explicit, such as a text button on the banner or the /chrome menu.

Ideally both. (2) also fixes the trap of × disconnecting when people expect it to dismiss.

Alternative Solutions

  • Clicking × removes the banner but disconnects Chrome. That's not acceptable if you want it connected.
  • Living with the banner. It takes up space above the input in every session and carries no information after the first time you see it.

No setting exists today. I checked the extension's contributes.configuration, the settings schema, the /chrome options and the Chrome integration docs.

Priority

Low - Nice to have

Feature Category

Configuration and settings

Use Case Example

  1. Enable Claude in Chrome with "Enabled by default", because browser tools are part of my normal workflow.
  2. Open a new Claude Code session in VS Code. The "Browser connected" banner appears.
  3. Click × to dismiss it, and Chrome is disconnected without warning.
  4. With this feature, the connection stays on, no banner appears while it's healthy, and I'd only see it on connecting/error.

Additional Context

  • Claude Code VS Code extension 2.1.289, macOS.
  • In webview/index.js, the banner renders whenever chromeMcpState.value.status !== "disconnected". Its close handler is onClose: () => { J.disableChromeMcp() } with closeTooltip: "Disconnect browser". No setting or stored flag controls whether it shows.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗