Skip to content

docs: note manual browser connection setup#373

Open
honor2030 wants to merge 1 commit into
browser-use:mainfrom
honor2030:docs/manual-first-run-browser
Open

docs: note manual browser connection setup#373
honor2030 wants to merge 1 commit into
browser-use:mainfrom
honor2030:docs/manual-first-run-browser

Conversation

@honor2030
Copy link
Copy Markdown

@honor2030 honor2030 commented May 18, 2026

Summary

  • add a short README note that browser-harness needs a connected browser before commands run
  • point manual users to the two safer connection paths already covered in install.md
  • avoid the unsafe bare --remote-debugging-port=9222 default-profile snippet

Test Plan

  • git diff --check origin/main...HEAD
  • uv run python -m compileall -q src tests

Closes #107


Summary by cubic

Clarifies manual first-run setup in README so browser-harness connects to a browser before any commands run. Points to the two safe connection options from install.md (normal profile via chrome://inspect/#remote-debugging, or isolated profile with --remote-debugging-port=9222 --user-data-dir=<path> and BU_CDP_URL) and avoids the unsafe bare default-profile flag.

Written for commit 5203dba. Summary will update on new commits. Review in cubic

Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

Re-trigger cubic

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.

[UX] Chrome remote debugging is a hidden prerequisite — not mentioned in README Quick Start

1 participant