New article "Let agents inspect w/ Chrome DevTools MCP"#3811
New article "Let agents inspect w/ Chrome DevTools MCP"#3811mikehoffms wants to merge 15 commits into
Conversation
| In this mode, you start Edge yourself (or it's already running), and the MCP server connects to it. This is useful when: | ||
|
|
||
| * You want to maintain browser state between manual testing and agent-driven testing. | ||
| * You need to be signed into a website that blocks automated browser launches. |
There was a problem hiding this comment.
I don't understand what we mean by a website that blocks automated browser launches. How can a website blocks this?
There was a problem hiding this comment.
What's meant by "a website that blocks automated browser launches". How can a website block automated browser launches?
|
Learn Build status updates of commit ec914bd: ✅ Validation status: passed
For more details, please refer to the build report. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
| <!-- ------------------------------ --> | ||
| #### "Could not connect to Chrome"<!-- todo: to Microsoft Edge? --> error with auto-connect | ||
|
|
||
| If you are using auto-connect and get an error such as "Could not connect to Chrome"<!-- todo: to Microsoft Edge? -->: |
There was a problem hiding this comment.
"Could not connect to Chrome" - to Microsoft Edge? 2x
There was a problem hiding this comment.
I suspect this string is coming from the Chrome DevTools MCP server. We're using this server to connect to Edge or WebView2, because it's inherently compatible with them, being Chromium-based, but we don't control what's in the Chrome DevTools MCP server itself. It may very well be that the server has that string "Could not connect to Chrome" hard-coded in it.
@zoherghadyali can confirm.
|
Learn Build status updates of commit 3457b47: ✅ Validation status: passed
For more details, please refer to the build report. |
captainbrosset
left a comment
There was a problem hiding this comment.
A few comments, and follow-up questions for Zoher, but otherwise LGTM. Approving already, I don't need to re-review once the remaining comments have been addressed.
| <!-- ---------- --> | ||
| ###### By using WebView2Utilities | ||
|
|
||
| In this approach, you use WebView2Utilities and follow the steps in [How to: Auto open DevTools](https://github.com/david-risney/WebView2Utilities/wiki/How-to:-Auto-open-DevTools). But instead of selecting the **Auto open DevTools** checkbox, in the **Arguments** textbox, enter `--remote-debugging-port=0`. |
There was a problem hiding this comment.
@zoherghadyali would you be ok if we inlined the wiki instructions? This would avoid potential confusion/context switching. The wiki isn't that long.
There was a problem hiding this comment.
| <!-- ------------------------------ --> | ||
| #### "Could not connect to Chrome"<!-- todo: to Microsoft Edge? --> error with auto-connect | ||
|
|
||
| If you are using auto-connect and get an error such as "Could not connect to Chrome"<!-- todo: to Microsoft Edge? -->: |
There was a problem hiding this comment.
I suspect this string is coming from the Chrome DevTools MCP server. We're using this server to connect to Edge or WebView2, because it's inherently compatible with them, being Chromium-based, but we don't control what's in the Chrome DevTools MCP server itself. It may very well be that the server has that string "Could not connect to Chrome" hard-coded in it.
@zoherghadyali can confirm.
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 88a90e9: ✅ Validation status: passed
For more details, please refer to the build report. |
Rendered article for review:
Let agents inspect your site and WebView2 app with Chrome DevTools MCP
/web-platform/devtools-mcp-server.mdAI for the web
/web-platform/index.mdtoc.ymlAB#62447540