Chrome DevTools MCP adds logpoints and network mocks for coding agents
Chrome DevTools MCP’s November 11 release gives browser-connected coding agents two practical debugging additions: logpoints and page-specific network mocks. Version 1.13.0 also supports upstream mock responses, according to the project’s official release notes.
The release includes an important boundary: the logpoint tool is disabled when JavaScript evaluation is disabled. Other fixes preserve binary request bodies and task serialization when requests are canceled.
Why it matters
Analysis: Giving an agent a browser is only part of the debugging problem. Controlled responses and extra diagnostic output can help developers reproduce a failure instead of asking the model to guess from a screenshot. These changes are infrastructure for investigation, not evidence that autonomous debugging now works reliably.
The evaluation-related restriction is also worth checking before enabling new tools in a development workflow. More observability should not quietly bypass an operator’s chosen execution limits.
Timing and evidence
This is newly covered November 11, 2026 software news, not a new November 16 launch. GitHub displays a release time of 12:40 without an explicit timezone. The features above are maintainer-reported; Guth News has not independently tested them, and no independent validation is cited.
Sources and citations
Revision history
Published .