browser-trace

原文涵盖的主题

• Browser Trace
• When to use
• Setup check
• How it works
• Quickstart
• Remote (Browserbase) sessions - not supported
• Filesystem layout
• Summary shape

Attach a second, read-only CDP client to a browser session that is already being driven by your main automation. The trace records the full DevTools firehose to NDJSON, polls for screenshots and DOM dumps in parallel, and slices everything into a directory tree that bash tools can search. This skill does not drive pages - it only listens. Pair it with agent-browser (the primary local driver, attached via agent-browser connect ), Playwright, Stagehand, or anything else that speaks CDP. 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. If the user just wants to drive the browser, use the agent-browser skill instead. No npm install is needed: the firehose and sampler are raw CDP over Node's built-in WebSocket. Every Chrome DevTools target accepts multiple concurrent CDP clients. Your main automation is one client; this skill adds a second one that only enable

这里只展示节选，请以完整原文和当前要求为准。