Skip to content

daemon: add Chrome Canary profile discovery#263

Open
femto wants to merge 1 commit intobrowser-use:mainfrom
femto:add-chrome-canary-support
Open

daemon: add Chrome Canary profile discovery#263
femto wants to merge 1 commit intobrowser-use:mainfrom
femto:add-chrome-canary-support

Conversation

@femto
Copy link
Copy Markdown

@femto femto commented Apr 30, 2026

Summary

  • Add Chrome Canary profile paths to PROFILES list for automatic DevToolsActivePort discovery
  • macOS: ~/Library/Application Support/Google/Chrome Canary
  • Windows: ~/AppData/Local/Google/Chrome SxS/User Data

Test plan

  • Verify daemon connects to Chrome Canary on macOS when both Chrome and Canary are running (Canary should take priority)
  • Verify daemon connects to Chrome Canary on Windows

🤖 Generated with Claude Code


Summary by cubic

Add Chrome Canary profile discovery so the daemon can auto-connect via DevToolsActivePort. Added macOS path ~/Library/Application Support/Google/Chrome Canary and Windows path ~/AppData/Local/Google/Chrome SxS/User Data, and keep stable Chrome ahead of Canary to avoid stale port files.

Written for commit 4bb1c59. Summary will update on new commits.

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.

1 issue found across 1 file

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="src/browser_harness/daemon.py">

<violation number="1" location="src/browser_harness/daemon.py:36">
P2: Putting Canary ahead of stable Chrome lets a stale `DevToolsActivePort` in Canary abort daemon startup before later, working Chrome profiles are tried.</violation>
</file>

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review, or fix all with cubic.

Comment thread src/browser_harness/daemon.py
@Alezander9
Copy link
Copy Markdown
Member

The cubic comment should be addressed before this is merged

Add Chrome Canary paths to PROFILES list so the daemon can discover
DevToolsActivePort from Canary installations:
- macOS: ~/Library/Application Support/Google/Chrome Canary
- Windows: ~/AppData/Local/Google/Chrome SxS/User Data

Stable profiles are listed before Canary to avoid stale Canary port
files blocking discovery (get_ws_url raises after 30s timeout).

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@femto femto force-pushed the add-chrome-canary-support branch from 88a7840 to 4bb1c59 Compare May 4, 2026 03:43
@femto
Copy link
Copy Markdown
Author

femto commented May 4, 2026

hello,resolved.

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.

2 participants