L⚠️ ◾ Integrate chrome devtools mcp features #251
Conversation
Integrates Chrome DevTools monitoring into the MCP server configuration. This allows for capturing console logs and network requests from a monitored Chrome instance during recordings. Includes UI elements to enable and launch the monitored Chrome browser. Co-authored-by: calumjs <calumjs@live.com>
|
Cursor Agent can help with this pull request. Just |
PR Metrics❌ Try to keep pull requests smaller than 400 lines of new product code by following the Single Responsibility Principle (SRP).
Metrics computed by PR Metrics. Add it to your Azure DevOps and GitHub PRs! |
github-actions
bot
changed the title
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
🚀 Pre-release build is available for this PR: |
Co-authored-by: calumjs <calumjs@live.com>
|
🚀 Pre-release build is available for this PR: |
Co-authored-by: calumjs <calumjs@live.com>
|
🚀 Pre-release build is available for this PR: |
Co-authored-by: calumjs <calumjs@live.com>
|
🚀 Pre-release build is available for this PR: |
Co-authored-by: calumjs <calumjs@live.com>
|
🚀 Pre-release build is available for this PR: |
Co-authored-by: calumjs <calumjs@live.com>
|
🚀 Pre-release build is available for this PR: |
Co-authored-by: calumjs <calumjs@live.com>
|
🚀 Pre-release build is available for this PR: |
Co-authored-by: calumjs <calumjs@live.com>
|
🚀 Pre-release build is available for this PR: |
This commit refactors the Chrome DevTools telemetry service to improve error handling and logging. It also adds a new `telemetryStartTimestamp` to filter out logs that occurred before telemetry started. Additionally, it sorts console and network logs by timestamp in the UI for better readability. Co-authored-by: calumjs <calumjs@live.com>
|
🚀 Pre-release build is available for this PR: |
Co-authored-by: calumjs <calumjs@live.com>
|
🚀 Pre-release build is available for this PR: |
Co-authored-by: calumjs <calumjs@live.com>
Co-authored-by: calumjs <calumjs@live.com>
Co-authored-by: calumjs <calumjs@live.com>
Co-authored-by: calumjs <calumjs@live.com>
|
🚀 Pre-release build is available for this PR: |
Co-authored-by: calumjs <calumjs@live.com>
|
🚀 Pre-release build is available for this PR: |
Co-authored-by: calumjs <calumjs@live.com>
|
🚀 Pre-release build is available for this PR: |
Co-authored-by: calumjs <calumjs@live.com>
|
🚀 Pre-release build is available for this PR: |
Co-authored-by: calumjs <calumjs@live.com>
|
🚀 Pre-release build is available for this PR: |
|
Closing PR, out of date |
✏️ Prompt: Institute the following feature: IF you have an MCP server for "chrome-devtools-mcp@latest" installed, THEN add a special checkbox only visible on that MCP server's settings page that says Enable Chrome MCP Test Mode WHEN enabled, DO THE FOLLOWING: A NEW BUTTON NEXT TO START RECORDING CALLED "OPEN MONITORED CHROME" appears... running this: & "C:\Program Files\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222 --user-data-dir="$env:TEMP\chrome-mcp-profile" (Obviously those params should be edited as necessary based on the MCP config) THEN WHEN THEY CLICK START RECORDING, STOP RECORDING, GRAB ALL THE CONSOLE LOGS AND NETWORK TRAFFIC (or the top N amount if sensible) and include with prompt context
Model: N/A
✏️ User request to add a "Chrome MCP Test Mode" feature for
chrome-devtools-mcpservers, enabling a monitored Chrome instance and capturing DevTools telemetry during recordings.✏️ - Added a "Enable Chrome MCP Test Mode" checkbox to MCP server settings, visible for
chrome-devtools-mcpservers.ChromeDevtoolsMonitorServiceto launch a monitored Chrome instance and capture DevTools console logs and network traffic.wsand@types/wsdependencies.✏️