adfcecf987
fix: validate and report incompatible Node versions ( #113 )
...
Ref https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/92
2025-09-24 14:45:27 +02:00
0ca2434a29
fix: forbid closing the last page ( #90 )
...
McpContext currently assumes that there is a page. Eventually we might
support closing the browser by closing the last page but right now we do
not really have responses that indicate that the browser was closed. So
this PR helps the LLM understand that it is okay to keep the last page
running (and there are platform-specific differences as to what happens
if the last page is closed).
Ref https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/87
2025-09-24 07:23:53 +00:00
1a4ba4d3e0
fix: add a message indicating that no console messages exist ( #91 )
...
To avoid clients being confused about the lack of console messages.
Closes https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/87
2025-09-23 22:10:46 +02:00
9c8da4a449
test: use cft for e2e tests ( #80 )
...
we were using the Chrome version pre-installed on the GitHub actions and
I wonder if it could have been the source for the flakiness.
2025-09-23 19:53:33 +02:00
92046183d4
chore(deps): bump puppeteer ( #79 )
...
Contains fixes for the pipe transport.
2025-09-23 17:01:19 +00:00
74fa209145
test: skip flaky test ( #77 )
2025-09-23 14:03:44 +00:00
e8fb30c1bf
fix: rework performance parsing & error handling ( #75 )
...
This PR tidies up the code around performance parsing and what we
respond with from our tools. It introduces the ability to have no
Insights from a trace (relatively rare, but can happen), and also adds
more information to the output in the event that something went wrong.
Previously we just logged errors, but if we respond with them here that
will also help users report issues and increase the chances that we can
debug them.
2025-09-23 15:42:35 +02:00
0208bfdcf6
fix: expose timeout when Emulation is enabled ( #73 )
...
Co-authored-by: Alex Rudenko <OrKoN@users.noreply.github.com >
2025-09-23 11:17:53 +02:00
91d83c4190
test: fix shell for windows tests ( #72 )
2025-09-23 09:37:22 +02:00
c509c64576
fix: increase timeouts in case of Emulation ( #71 )
2025-09-22 18:13:49 +02:00
a9cf9d77f7
test: await dialog dismiss to prevent async activity errors ( #70 )
2025-09-22 17:11:04 +02:00
1e8662f068
fix(emulation): correctly report info for selected page ( #63 )
...
Previously if one page was setting emulation all were reporting it.
2025-09-22 16:03:47 +02:00
b830b436f9
chore: roll devtools-frontend and update snapshots ( #59 )
2025-09-22 09:29:21 +00:00
21e175b862
feat: add performance_analyze_insight tool. ( #42 )
2025-09-17 12:25:40 +00:00
0cb6147b87
feat: use Performance Trace Formatter in trace output ( #36 )
...
Note: this will error until a chrome-devtools-frontend with this change
https://chromiumdash.appspot.com/commit/62e1652b2bf044ec53a2ec212cf53b1a62bc357e
is released on npm.
2025-09-16 17:07:58 +00:00
c663f4d7f9
feat: support script evaluate arguments ( #40 )
...
This change allows clients to pass snapshot elements as arguments.
2025-09-16 17:44:53 +02:00
014a8bc52e
feat: validate uids ( #37 )
...
- generate snapshot IDs.
- change uid to be a string.
- validate that uid is not coming from a stale snapshot.
2025-09-16 11:54:35 +00:00
3fcea791eb
chore: roll puppeteer ( #25 )
...
This should solve flakiness related to multiple browser instances.
2025-09-15 16:12:13 +02:00
e5e0616433
chore: switch to spec and clean up deps ( #17 )
2025-09-15 11:18:32 +02:00
732267db5f
fix: detect multiple instances and throw ( #12 )
...
We should be checking for browser logs in Puppeteer instead.
2025-09-11 16:42:27 +02:00
31a0bdce26
feat: initial version
2025-09-11 12:46:05 +02:00
Alex Rudenko