sightmap console and sightmap network read the browser activity captured during a session. The browser start daemon runs a collector: a session-lifetime CDP client that attaches to every tab and buffers console messages and network requests into bounded ring buffers (the most recent ~1000 of each). These commands query that buffer over the daemon’s HTTP server.
Devtools commands require a running
browser start session — the collector lives in that daemon. With no session they print no running session — start one with 'sightmap browser start'. Entries captured before the session started are not available.list reports as (N earlier entries dropped — buffer overflowed).
console list
Lists captured console messages, oldest to newest. Uncaught exceptions are folded in as level exception.
[index] level text. When entries span multiple tabs, the tab ID is shown too. The index is stable — pass it to console get.
console get
Prints one console message by index.
network list
Lists captured network requests, oldest to newest.
[index] method url → status (resourceType). Requests with no response yet show pending.
network get
Prints one request’s metadata by index, then its response body. Bodies are fetched on demand from the collector connection that observed the request.
--response-file, network get previews the first few KB of the response body inline.
Typical flow
1
Start a session
sightmap browser start — the collector begins capturing as soon as Chrome is ready.2
Reproduce the issue
Drive the page with interaction commands or in the browser window.
3
Read the evidence
sightmap console list --level error and sightmap network list --type XHR surface what failed; network get INDEX pulls the response body.