I build AI agent systems, browser automation tools, and local-first developer workflows.

Local replay debugger for Browser Use failures.

BrowserTrace helps Browser Use builders debug failed runs with local step timelines: what the agent saw, clicked, returned, and where the first red step happened. Stagehand, Skyvern, Playwright + LLM, and custom computer-use workflows are supported as secondary integrations.

• Records screenshots, URLs, actions, model input/output, status, and errors.
• Opens failed runs in a local web UI.
• Compares failed-vs-good Browser Use runs with browsertrace compare.
• Exports standalone HTML traces.
• Supports public-safe exports that omit prompts, model I/O, screenshots, and URLs.
• Browser Use run hooks are the primary integration path.
• Supports the Stagehand wrapper and the Skyvern task/workflow wrapper.
• Includes Playwright + LLM examples and custom computer-use examples.
• Listed in Awesome-AI-Agents under Applications -> Tools.
• MIT licensed and local-first.

Repo: https://github.com/aaronlab/browsertrace

Live demo: https://aaronlab.github.io/browsertrace/

Demo story: Browser Use tries to upload file:///tmp/browsertrace-report.html, navigates to the local file path instead, and the upload preview never appears.

Try locally from PyPI:

uvx --from "browsertrace[ui]" browsertrace doctor
uvx --from "browsertrace[ui]" browsertrace demo
uvx --from "browsertrace[ui]" browsertrace

Persistent install:

pip install "browsertrace[ui]"
browsertrace doctor
browsertrace demo
browsertrace

Stack guides:

• Browser Use: https://aaronlab.github.io/browsertrace/browser-use-debugging.html
• Stagehand: https://aaronlab.github.io/browsertrace/stagehand-debugging.html
• Skyvern: https://aaronlab.github.io/browsertrace/skyvern-debugging.html
• Playwright + LLM: https://aaronlab.github.io/browsertrace/playwright-llm-debugging.html
• Computer-use: https://aaronlab.github.io/browsertrace/computer-use-agent-debugging.html

Runnable examples: https://github.com/aaronlab/browsertrace/tree/main/examples

Roadmap: https://github.com/aaronlab/browsertrace/blob/main/ROADMAP.md

Launch feedback: aaronlab/browsertrace#3

Good first issue: https://github.com/aaronlab/browsertrace/labels/good%20first%20issue

First PR Recipe: https://github.com/aaronlab/browsertrace/blob/main/CONTRIBUTING.md#first-pr-recipe keeps the first contribution small and reviewable.

Public-safe demo export: https://github.com/aaronlab/browsertrace/releases/download/v0.1.20/browsertrace-demo-public.html

For profile-reader follow-up, local first-run issues, CI failures, or AI/coding-agent troubleshooting replies, ask for debugging/workflow details plus JSON CLI diagnostics when safe to share:

browsertrace doctor --json
browsertrace list --status failed --json
browsertrace show <run_id> --json

Use the closest guide when a profile-reader follow-up turns into a workflow-specific debugging question:

• Browser Use guide: https://aaronlab.github.io/browsertrace/browser-use-debugging.html
• Stagehand guide: https://aaronlab.github.io/browsertrace/stagehand-debugging.html
• Skyvern guide: https://aaronlab.github.io/browsertrace/skyvern-debugging.html
• Playwright + LLM guide: https://aaronlab.github.io/browsertrace/playwright-llm-debugging.html
• Computer-use guide: https://aaronlab.github.io/browsertrace/computer-use-agent-debugging.html

• Browser Use failure debugging
• Browser automation and computer-use agents
• LLM observability for local workflows
• Agent evaluation and tool reliability

If you build with Browser Use, the most useful BrowserTrace feedback is:

• Which Browser Use failure shape hurts most?
• What context is missing when a run fails?
• Are local HTML exports enough, or do you need hosted share links?
• Which secondary adapter should be improved first?

Launch discussion: aaronlab/browsertrace#6