fix(browser): add URL-based fallback for extension relay tab matching #1999
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
When using the Chrome extension relay (
profile=chrome), browser actions likesnapshotfail with "tab not found" even thoughtabscorrectly lists all attached tabs.Root Cause
Playwright's
newCDPSession(page)usesTarget.attachToBrowserTargetto create CDP sessions for mapping pages to targetIds. Chrome's extension debugger API blocks this method with:This causes
findPageByTargetId()to fail for all pages.Solution
Add a fallback in
findPageByTargetId()that:/json/listendpointTesting
Tested locally with 9 attached Chrome tabs, including multiple tabs with the same URL. The fix correctly matches pages to targetIds.
Fixes #1998
🤖 This bug was discovered by Claude Code running inside Clawdbot, and the fix was developed and submitted with human oversight.