Skip to content

fix(browser): suggest custom profiles for missing port files - #3496

Open
AmarGhugare wants to merge 1 commit into
ChromeDevTools:mainfrom
AmarGhugare:fix/autoconnect-profile-hint
Open

AmarGhugare wants to merge 1 commit into
ChromeDevTools:mainfrom
AmarGhugare:fix/autoconnect-profile-hint

Conversation

@AmarGhugare

Copy link
Copy Markdown

Fixes #889.

When channel-based auto-connect cannot find the default profile's DevToolsActivePort file, suggest --user-data-dir for a custom profile. Keep the existing running-browser/remote-debugging guidance and the original error cause.

Only add the hint for a missing-file (ENOENT) cause. Puppeteer uses the same outer message for malformed port files and refused connections, where changing the profile would be misleading. Permission failures also keep their existing behavior; those are covered separately by #3487. The README guidance for #889 was already updated in #3386.

Validation on Windows, Node 24.19.0, Chrome 157.0.8103.78:

  • Updated missing-file regression fails before the fix; controls cover EPERM, EACCES, malformed files, and refused connections.
  • npm run test -- tests/browser.test.ts: 41 passed.
  • npm run format: passed.
  • npm run test: 1,985 passed, 5 skipped, zero failures.

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.

The DevTools MCP is hardcoded to look for Chrome in standard locations

1 participant