All features
Debug with vidspawn
The bug report that carries its own evidence.
Record the Chrome window while you reproduce the bug and vidspawn captures the console logs, page errors and network requests firing inside it, timestamped against the video. If you know Jam, this is that workflow, open source: the evidence lands in your local library next to the recording, not in a vendor cloud.
What gets captured
Console output, uncaught page errors and network requests from the recorded Chrome window, each stamped against the video timeline.
Click a line, watch the moment
The Dev tab shows Console and Network alongside the player. Click an entry and the video seeks to the moment it fired. The raw log exports too.
Readable by your agent
get_console_logs and get_network_requests are on the MCP surface. Ask your agent to find the failed checkout and pull the errors from that take.
An extension you can read
Telemetry streams from a companion Chrome extension that lives in the repo. Its one permitted host is 127.0.0.1, it streams while a devtools-enabled recording is live and at no other time, and it is AGPL like everything else.
Watch what you did. Read what the page did. One recording.
See the full vidspawn vs Jam comparison