Chrome DevTools console logs missing from browser-tools-server/getConsoleLogs
With @agentdeskai/browser-tools-server and the Chrome extension (reported on macOS Sequoia 15.3.2, Chrome 134, Cursor 0.48.7, and also on Chrome 138 arm64 and Windows), the server receives selected-element and network-request logs, but consoleLogs and consoleErrors stay at 0. Chrome DevTools clearly shows console messages and errors, yet getConsoleLogs returns no error entries. Why are console logs not captured, and is there a fix?
Originally asked on GitHub: https://github.com/AgentDeskAI/browser-tools-mcp/issues/51
5 answers
Still unresolved: the GitHub issue was closed as NOT_PLANNED, and the thread contains no fix, workaround, or maintainer explanation.
The reporter ran
npx @agentdeskai/browser-tools-server; the server log shows the Chrome extension connecting via WebSocket to the aggregator athttp://127.0.0.1:3025and processingselected-elementandnetwork-requestentries (for exampleGET http://localhost:3000/models/40425-cs-stkr_R13.gltfwith status 304). Throughout,consoleLogs: 0andconsoleErrors: 0stay at zero even though Chrome DevTools shows console messages. The same symptom was reported on macOS Sequoia 15.3.2 with Chrome 134 and Cursor 0.48.7, on macOS 15.3 with Chrome 138 (arm64), and on Windows with a Next.js app, wheregetConsoleLogsreturned other logs but not the error logs visible in DevTools. On another setup, 165 successful network requests and screenshots were captured whileconsoleLogsremained 0, so network and screenshot capture worked but console capture did not.No configuration change or version pin from this thread fixes it. As general advice (not verified in this thread), you could try a hard reload of the page after the extension connects and check whether the missing messages come from a page or iframe context the extension does not capture; otherwise watch the repository for a future fix.
Did this work for you?What a GitHub user tried on GitHub (Didn't work)
Started the server with
npx @agentdeskai/browser-tools-server; the extension connected and sent selected-element/network-request logs, but consoleLogs and consoleErrors stayed 0 while DevTools showed console messages.Source: https://github.com/AgentDeskAI/browser-tools-mcp/issues/51 (opens external site)
Did this work for you?What @smilingkylan tried on GitHub (Didn't work)
On macOS Sequoia 15.3.2 with Chrome 134 and Cursor 0.48.7: network requests (165 successes) and screenshots were captured, but consoleLogs remained 0.
Did this work for you?What @Defozo tried on GitHub (Didn't work)
On Windows with a Next.js app,
getConsoleLogsreturned other logs but not error logs, even though DevTools showed an Uncaught Error and a 500 response.Did this work for you?What @bitcoinvsalts tried on GitHub (Outcome unclear)
Clicked the screenshot capture button in the Chrome extension and received errors from the extension (error screenshot attached in the thread).
Did this work for you?
Related questions
- browser-tools-mcp in Cursor: "spawn npx ENOENT" and no tools found
- Why can't the AI view or analyze a screenshot taken by browser-tools-mcp in Cursor?
- browser-tools-mcp in Cursor: 'Error validating server identity' after macOS update — fix?
- How to fix "Failed to discover browser connector server" in browser-tools-mcp?
- browser-tools-mcp: getConsoleLogs returns empty although DevTools shows console errors