Browser Trace

Capture a full DevTools-protocol trace of any browser automation — CDP firehose, screenshots, and DOM dumps — then bisect the stream into per-page searchable buckets. Use when the user wants to debug a failed run, audit network/console/DOM activity, attach a trace to an in-progress session, or feed structured per-page

Overview

Browser Trace is a specialized utility for AI agents, part of the mxyhi/ok-skills repository. It enables comprehensive monitoring of browser automation by capturing full DevTools-protocol traces. The tool records a Chrome DevTools Protocol (CDP) firehose, including screenshots and DOM dumps, which it then organizes into searchable, page-specific buckets. This functionality allows developers to audit network activity, console logs, and DOM states across different session stages. Compatible with agents like Claude, Cursor, and Codex, it provides structured data for debugging failed automation runs or auditing in-progress sessions. By bisecting the data stream, it simplifies the analysis of complex web interactions, making it easier to feed per-page context back into AI models for more accurate troubleshooting.

Use Cases

Debugging failed automation runs by reviewing captured CDP logs and DOM states.
Auditing network and console activity during active AI agent browser sessions.
Generating structured per-page data buckets for historical session analysis.

Install Notes

# Review source first
open https://github.com/mxyhi/ok-skills/blob/main/browser-trace/SKILL.md

Copy or clone the skill folder into your agent skills directory after reviewing its instructions and scripts.

Security Notes

Users should be aware that capturing full DevTools-protocol traces, including DOM dumps and screenshots, may record sensitive information visible during the browser session. Access to the resulting data buckets should be restricted to authorized users to prevent exposure of credentials or private data captured during the automation process.

Related Skills