Michael Hablich
Michael Hablich
Relevant: https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/395
This is also needed for proper device emulation.
This should likely work similar to how we send back screenshots. If they are over a limit, we store them in a file.
https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/338 should have solved this, right?
@OrKoN does the --no prefix work for this use case?
I think this needs to be optional, not every click results in a reload of the whole tree and returning the whole tree will just consume tokens like crazy.
Have you tried letting the agent use evaluate_script with ```document.body.style.zoom = 0.5;```?
viewport, cpu and network throttling can already be set via emulate and resize_page. Have you tried simply saying in the prompt something like "Open this URL example.com, emulate that your...
Do you mean that you can select an element/artifact in Chrome DevTools and use it as context in your MCP client?
Understood, so the human would then use the selected element to continue debugging on their own in DevTools?