482a288c7e
chore: evaluate select_page scenario ( #925 )
...
Passes the test with gemini-2.5-flash with no errors.
Closes https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/921
2026-02-10 10:11:23 +00:00
aa0a3679f5
feat: add a skill for using chrome-devtools-mcp ( #830 )
...
Closes https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/710
Closes https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/709
2026-01-26 10:04:39 +00:00
aa9a176956
fix: improve performance tool description ( #800 )
...
Drive-by: refactor and improve eval scripts.
2026-01-20 11:38:51 +00:00
67c1f80b28
chore: refactor eval script more ( #781 )
...
add args parsing and simplify output (support debug logging + headless).
2026-01-16 08:49:06 +00:00
0284d18b7b
chore: support an html route in evals ( #770 )
...
Allows using the server URL in the prompt.
2026-01-14 17:11:53 +00:00
257b9943e9
chore: add basic eval ( #766 )
...
This PR adds a tool based on the node test runner that runs a loop to
see what tools a model chooses given a prompt. The expectations are
encoding for each prompt. Run `npm run eval` to get results. Currently,
only Gemini and needs and API key.
2026-01-14 14:15:21 +00:00
Alex Rudenko