browser-trace

Community

Attach a read-only browser trace to debug runs.

Authorvanducng
Version1.0.0
Installs0

System Documentation

What problem does it solve?

Debugging browser automation runs can be challenging due to intermittent CDP events, hidden network/console activity, and DOM state. Browser Trace provides a non-intrusive, read-only trace that records the entire DevTools protocol stream alongside periodic screenshots and DOM dumps, so you can inspect what happened at any moment.

Core Features & Use Cases

  • Attach a second, read-only CDP client to a live browser session to capture a complete firehose of events (Network, Console, Runtime, Page, Log) without altering the main automation.
  • Automatically generate per-page buckets with per-page raw events, plus page-level summaries, screenshots, and DOM snapshots for targeted debugging across navigations.
  • Reproduce production issues, audit activity, or attach traces to in-progress sessions to build post-mortem analyses and improve agent learning loops.

Quick Start

Start a trace against a local Chrome session and capture the firehose with per-page snapshots for debugging.

Dependency Matrix

Required Modules

None required

Components

scripts

💻 Claude Code Installation

Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.

Please help me install this Skill:
Name: browser-trace
Download link: https://github.com/vanducng/skills/archive/main.zip#browser-trace

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository

Agent Skills Search Helper

Install a tiny helper to your Agent, search and equip skill from 510,000+ vetted skills library on demand.