Skip to content

BrowserZap 0.5 is out on npm for Windows · Chrome Web Store listing in review · Get started

BrowserZap

Docs

Console and network

Next release. This is built and tested, and ships in the next version. Version 0.5.0 on npm does not have it yet; this page will drop the note when it does.

When your agent debugs your app, it can read what the page logged and requested — the two things developers ask browser agents for most. Try: "Open my app, click Save, and tell me why it fails: check the console and the network."

page_console

Console messages of the session's tab, newest last: console.log, warnings, errors, uncaught exceptions with file and line, and the browser's own messages (failed loads, blocked content, deprecations).

page_console { "level": "error" }
→ 3 console message(s); 3 error(s) among them.
  error · exception · TypeError: Cannot read properties of undefined (reading 'map') · app.js:118
  error · browser  · Failed to load resource: the server responded with a status of 500
  • level: all, warning (warnings and errors) or error; contains filters by text; limit up to 200.
  • clear: true empties the buffer after reading, so the next call shows only what is new.
  • The first call turns console capture on for that tab, and Chrome replays what the page logged before. It is off until then because some bot-detection scripts can notice it.

page_network

Requests the tab made while BrowserZap was attached (every navigation attaches it): method, URL, type, status, duration, size and failure reason.

page_network { "failedOnly": true }
→ 2 request(s); 2 failed or 4xx/5xx.
  GET  /api/orders?page=2   Fetch  500  412 ms
  POST /api/save            Fetch  failed: net::ERR_CONNECTION_REFUSED
  • failedOnly keeps failed and 4xx/5xx requests; types (XHR, Fetch, Document, Script…) and urlContains filter.
  • If nothing is recorded, navigate or reload the page and ask again.

Privacy

  • Headers, cookies and request or response bodies are never read.
  • Query strings are kept only for requests to the page's own site; other sites show address and path only.
  • Kept in memory per tab (up to 300 messages and 400 requests), never written to a log.
  • Message text comes from the page and is labelled untrusted for the agent.