Skip to content

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

Closed
MukundaKatta wants to merge 3 commits intoChromeDevTools:mainfrom
MukundaKatta:codex/chrome-cli-autoconnect-clarify
Closed

docs(cli): clarify how to attach to an existing Chrome instance#1929
MukundaKatta wants to merge 3 commits intoChromeDevTools:mainfrom
MukundaKatta:codex/chrome-cli-autoconnect-clarify

Conversation

@MukundaKatta
Copy link
Copy Markdown
Contributor

Summary

  • clarify that chrome-devtools start does not accept --autoConnect
  • point users to --browserUrl when they want to attach to an already running Chrome instance

Why

The CLI docs already describe supported daemon startup arguments, but it is easy to assume that --autoConnect is available here as well. Calling out the intended --browserUrl workflow makes the attachment path clearer for CLI users.

@MukundaKatta
Copy link
Copy Markdown
Contributor Author

Withdrawing — low-value drive-by docs change. Apologies for the noise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant