BrowserTrace

Agent-enablingOpen Source

Local failure timeline debugger for AI browser-agent runs

BrowserTrace preview

Overview

About BrowserTrace

This summary uses submitted and public product material. Only source-mapped claims are documentation reviewed.

BrowserTrace is an open-source local debugger for AI browser-agent failures. It records each run as a step timeline with screenshot, URL, action, model input/output, status, and error context, then exports standalone HTML traces with public-safe redaction. The project is built around Browser Use, Stagehand, Skyvern, Playwright + LLM scripts, and custom computer-use agents.

Features

  • Local step timeline for AI browser-agent runs, including screenshots, URLs, actions, model I/O, status, and errors
  • browsertrace doctor, browsertrace demo, browsertrace list, browsertrace show, and self-contained HTML export commands
  • Public-safe export mode that omits model I/O, screenshots, and URLs for issue or PR attachments
  • Browser Use, Stagehand, Skyvern, Playwright + LLM, and custom computer-use agent examples or wrappers
  • Local-first SQLite trace store with no hosted account required

Allows you to create agents that…

  • Produce inspectable failure artifacts when a browser task breaks
  • Debug model decisions alongside the exact browser state an agent saw
  • Share sanitized traces with maintainers or teammates without exposing private prompts, screenshots, or URLs

Listing decision

Why BrowserTrace is listed

BrowserTrace records and presents evidence from another browser agent’s execution so developers or agents can diagnose failures; it is observability and debugging support rather than an autonomous task agent.

Before you choose

Fit and limitations

Best for

Developers debugging failed Browser Use runs who need the browser state, action, model input/output, status, and error in one local timeline, with secondary support for other browser-agent workflows.

Known limitations

Python 3.11+ is required. Browser Use is the primary integration and the others are secondary; public-safe exports intentionally omit prompts, screenshots, and URLs, and BrowserTrace does not upload trace files for the user.

Not yet verified

The repository describes hosted team features as coming soon, so they are not treated as current capabilities. No independent integration-coverage or performance benchmark was found in the reviewed sources.

Sources

Sources and verification

First-party unless marked otherwise. Each link supports only its adjacent claim.

  1. BrowserTrace repository — capture model, commands, and local storage

    The maintained repository documents a Python 3.11+ local debugger with a CLI, web UI, SQLite and filesystem storage, JSON access, run comparison, and redacted HTML exports.

    official repository · accessed Sep 3, 2026
  2. BrowserTrace integrations — primary and secondary adapter scope

    Browser Use is the primary integration, while Stagehand, Skyvern, Playwright plus LLM, and custom computer-use flows are documented as secondary or generic integrations.

    official documentation · accessed Sep 3, 2026
  3. BrowserTrace license — MIT

    BrowserTrace is published under the MIT License.

    official license · accessed Sep 3, 2026

Related tools

Comments