From 3ad6e4f438e334ffaf498e8ecc745cd1c67e65c7 Mon Sep 17 00:00:00 2001
From: Sebastian Benz <sbenz@google.com>
Date: Thu, 18 Dec 2025 19:00:26 +0100
Subject: [PATCH] docs: autoConnect - clarify how the mcp server selects a
 profile

---
 README.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index e07cb7e5b..45ca0f86c 100644
--- a/README.md
+++ b/README.md
@@ -533,7 +533,8 @@ Make sure your browser is running. Open gemini-cli and run the following prompt:
 Check the performance of https://developers.chrome.com
 ```
 
-Note: The <code>autoConnect</code> option requires the user to start Chrome.
+> [!NOTE]  
+> The <code>autoConnect</code> option requires the user to start Chrome. If the user has multiple active profiles, the MCP server will connect to the default profile (as determined by Chrome). The MCP server has access to all open windows for the selected profile.
 
 The Chrome DevTools MCP server will try to connect to your running Chrome
 instance. It shows a dialog asking for user permission.