Skip to content

fix-chrome-connection: document chrome-devtools-mcp extension-debugging (Chrome-149-gated)#27

Merged
MichalOpsAgents merged 1 commit into
mainfrom
card-0nfcts9J-fix-chrome-extension-debugging
May 31, 2026
Merged

fix-chrome-connection: document chrome-devtools-mcp extension-debugging (Chrome-149-gated)#27
MichalOpsAgents merged 1 commit into
mainfrom
card-0nfcts9J-fix-chrome-extension-debugging

Conversation

@MichalOpsAgents

Copy link
Copy Markdown
Contributor

Documents the DevTools 148 / chrome-devtools-mcp v1.1.1 Extensions tool category in the fix-chrome-connection skill.

What changed: new Known Issues subsection + skill bump v1.1.2 → v1.1.3.

Why it's documentation, not active wiring: the extension tools (list_extensions, reload_extension, ...) only work over a pipe connection. Attach mode (browserUrl/wsEndpoint/autoConnect) is unsupported until Chrome 149, and this skill debugs an already-running Chrome (attach mode). Local Chrome is 148.0.7778.181, so the live-bridge diagnostic is gated until 149 ships.

The section records: the cheap version re-check command, and the planned list_extensions/reload_extension service-worker diagnostic to wire in ahead of the 0.sock symlink surgery once Chrome ≥ 149.

Card: https://trello.com/c/0nfcts9J

🤖 Generated with Claude Code

…ng (Chrome-149-gated)

DevTools 148 added a 5-tool Extensions category to chrome-devtools-mcp
(verified v1.1.1: list_extensions / reload_extension / trigger_extension_action
/ install_extension / uninstall_extension behind --categoryExtensions).

The tools only work over a pipe connection; attach mode (browserUrl/wsEndpoint/
autoConnect) is unsupported until Chrome 149. This skill debugs an already-running
Chrome (attach mode), so the live bridge extension can't be inspected until 149
ships (local Chrome is 148.0.7778.181).

Adds a Known Issues subsection with the cheap version re-check command and the
planned list_extensions/reload_extension diagnostic to wire in once Chrome >= 149,
ahead of the 0.sock symlink surgery / manual re-auth path. Bumps skill to v1.1.3.

Card: https://trello.com/c/0nfcts9J

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code Review

This pull request updates the SKILL.md documentation to version 1.1.3 and adds a section detailing future diagnostics using chrome-devtools-mcp extension debugging tools once Chrome 149 is released. The review feedback points out that the defaults read command used to check the Chrome version on macOS should omit the .plist extension to avoid potential lookup failures.


**Re-check the gate (cheap, run before assuming it's still closed):**
```bash
defaults read "/Applications/Google Chrome.app/Contents/Info.plist" CFBundleShortVersionString

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

Using defaults read with a .plist extension can fail on macOS because the defaults utility automatically appends .plist to the path, resulting in a search for Info.plist.plist. To ensure compatibility and avoid errors, omit the .plist extension from the path.

Suggested change
defaults read "/Applications/Google Chrome.app/Contents/Info.plist" CFBundleShortVersionString
defaults read "/Applications/Google Chrome.app/Contents/Info" CFBundleShortVersionString

@MichalOpsAgents MichalOpsAgents merged commit 0c5b88d into main May 31, 2026
5 checks passed
@MichalOpsAgents MichalOpsAgents deleted the card-0nfcts9J-fix-chrome-extension-debugging branch May 31, 2026 17:02
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