feat: add browser extension context debugging support #714
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
Tasktivity
force-pushed
the
feature/extension-debugging
branch
from
314d2df to
92ab6b3
Compare
Add --enableExtensions flag to enable debugging of Chrome extension contexts. New capabilities: - Extension pages (sidepanels, popups, options pages) visible in list_pages - Service workers listed in dedicated section - New open_extension_sidepanel tool to open sidepanel in detached window - Full debugging support: snapshots, console, script evaluation Due to Chrome security requirements, chrome.sidePanel.open() requires a user gesture and cannot be triggered via CDP. The open_extension_sidepanel tool uses chrome.windows.create() as the standard workaround, opening the sidepanel in a detached popup window with identical code execution. Partially Addresses ChromeDevTools#96
Tasktivity
force-pushed
the
feature/extension-debugging
branch
from
92ab6b3 to
ed85500
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Implements browser extension context debugging as requested in #96.
This PR adds the ability for AI coding assistants to inspect, debug, and interact with Chrome extension components including service workers, sidepanels, popups, and extension pages.
New Features
--enableExtensionsflaglist_pagesopen_extension_sidepanelScope
This PR implements extension context debugging as requested in #96:
Not Included (Future Work)
Known Chrome Limitations
The following requested features are not technically feasible due to Chrome security restrictions:
click_extension_icon- Browser toolbar is outside CDP's accessible viewport (puppeteer#2486)click_extension_context_menu- Context menus are browser UI elements, inaccessible via CDPThese are fundamental browser security constraints, not implementation gaps.
Testing
list_pages✓select_pageworks for extension contexts ✓take_snapshotcaptures extension UI ✓click,fill,hoverwork on extension elements ✓evaluate_scriptexecutes in extension context ✓Usage
# Enable extension debugging npx @anthropic-ai/claude-code-mcp chrome-devtools --enableExtensionsPartially Addresses #96