browser-trace
browser trace
What it does
- The user wants to debug a browser-automation run (failing form, missing element, hung navigation, JS exception).
- The user has a running automation and wants to attach a trace mid-flight without restarting it.
- The user wants to split a CDP firehose into network / console / DOM / page buckets.
- The user wants screenshots + DOM snapshots over time, joined to CDP events by timestamp.
- <run>/browserbase/session.json — final browse cloud sessions get snapshot (proxyBytes, status, endedat, viewport, …)
- <run>/browserbase/logs.json — browse cloud sessions logs output. Often empty. The CDP firehose in cdp/raw.ndjson is the source of truth; this is a side channel.
- <run>/browserbase/downloads.zip — files the session downloaded, if any (the script discards the empty 22-byte zip you get when there are none)
Requirements & configuration
- node --version # require Node 18+
Configuration: CONNECT_URLBROWSE_NAMEO11Y_DOMAINSCOMPLETEDBB_SESSION_TIMEOUT
Derived from the skill's own SKILL.md documentation · extracted 2026-07-23
browser-trace FAQ
What does the browser-trace skill do?
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 summaries back into an agent loop so its next iteration learns from the last one. The user wants to debug a browser-automation run (failing form, missing element, hung navigation, JS exception). The user has a running automation and wants to attach a trace mid-flight without restarting it.
What does browser-trace require?
node --version # require Node 18+ Configuration keys: CONNECT_URL, BROWSE_NAME, O11Y_DOMAINS, COMPLETED, BB_SESSION_TIMEOUT.
How do I install browser-trace?
Run: npx -y skills add https://github.com/browserbase/skills --skill browser-trace --agent claude-code — the source lives at github.com/browserbase/skills.
Maintain browser-trace?
Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.
[browser-trace on getagentictools](https://getagentictools.com/skills/browserbase-skills-browser-trace?ref=badge) npx agentictools info skills/browserbase-skills-browser-trace The second line is the CLI lookup for this page — handy in READMEs and docs.
