browser-trace

Capture browser automation traces into searchable JSONL files.

3.7k|235|Updated Oct 12, 2025
One-click install
npx skills add https://github.com/browserbase/skills --skill browser-trace-browserbase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-trace
Source: https://github.com/browserbase/skills/tree/main/skills/browser-trace
Command: npx skills add https://github.com/browserbase/skills --skill browser-trace-browserbase

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires browse, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill captures detailed traces of browser automation activities, enabling users to debug and audit their automation runs efficiently.

Core Features & Use Cases

  • Full DevTools Protocol Trace: Record a comprehensive trace of all browser automation interactions.
  • Per-Page Buckets: Organize trace data by page, making it easier to analyze specific sections of a browser automation run.
  • Searchable JSONL Files: Export trace data into searchable JSONL files for further analysis with command-line tools.
  • Use Case: If a browser automation script fails to complete a task, this Skill can be used to capture the trace, which can then be analyzed to identify the issue.

Quick Start

To capture the trace of a browser automation run, use the browser-trace skill and specify the run ID with the command: browser-trace capture <run-id>

Frequently Asked Questions about browser-trace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture a DevTools Protocol trace for browser automation debugging?

To capture a DevTools Protocol trace for browser automation debugging, use the browser-trace skill and specify the run ID with the command: browser-trace capture <run-id>. It records a comprehensive trace of all browser automation interactions.

Why does my browser automation script fail to complete a task and how can I identify the issue?

When a browser automation script fails, you can capture and analyze the trace data to identify the issue. The browser-trace skill records network, console, and DOM activity, organizing data into per-page buckets for easier debugging.

Can I export browser automation trace data into searchable files for command-line analysis?

Yes, you can export browser automation trace data into searchable JSONL files for further analysis with command-line tools. This allows you to parse network, console, and DOM activity logs efficiently after the run completes.

Do I need the browse CLI to run JavaScript code during a browser automation trace?

Yes, capturing browser automation traces requires the browse CLI and the ability to run JavaScript code within the browser's context. These prerequisites enable the skill to record detailed DevTools Protocol activity.

What's the best way to organize trace data by page during a browser automation run?

The best way to organize trace data by page is using per-page buckets. The browser-trace skill automatically structures recorded network, console, and DOM activity into these buckets, making it easier to analyze specific sections of a run.

What is a full DevTools Protocol trace and when do I need it for browser automation?

A full DevTools Protocol trace is a comprehensive recording of all browser automation interactions via CDP. You need it when auditing automation runs or debugging scripts that fail, providing insights into network, console, and DOM activity.