Skip to content

docs(cli): clarify how to attach to an existing Chrome instance #1929

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
MukundaKatta wants to merge 3 commits into from
+3 −0
Closed

docs(cli): clarify how to attach to an existing Chrome instance #1929

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
512854e
docs: clarify CLI autoConnect support
MukundaKatta Apr 18, 2026
fb7b436
Merge branch 'main' into codex/chrome-cli-autoconnect-clarify
MukundaKatta Apr 22, 2026
f0a84e9
Merge branch 'main' into codex/chrome-cli-autoconnect-clarify
MukundaKatta Apr 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/cli.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,9 @@ The CLI acts as a client to a background `chrome-devtools-mcp` daemon (uses Unix
- **Persistence**: The same background instance is reused for subsequent commands, preserving the browser state (open pages, cookies, etc.).
- **Manual Control**: You can explicitly manage the background process using `start`, `stop`, and `status`. The `start` command forwards all subsequent arguments to the underlying MCP server (e.g., `--headless`, `--userDataDir`) but not all args are supported. Run `chrome-devtools start --help` for supported args. Headless is enabled by default. Isolated is enabled by default unless `--userDataDir` is provided.

> [!NOTE]
> The CLI intentionally does not support `--autoConnect` on `chrome-devtools start`. If you need to attach to an already running Chrome instance, use `chrome-devtools start --browserUrl http://127.0.0.1:9222` instead.

```sh
# Check if the daemon is running
chrome-devtools status
Expand Down