Summary

Add BrowserTrace as a local-first debugging trace viewer for AI web-agent runs.

Item

• Name: BrowserTrace
• Link: https://github.com/aaronlab/browsertrace

Section

Dev Tools

Why this belongs

BrowserTrace directly supports operating and debugging web agents by recording Playwright, Browser Use, Stagehand, Skyvern-shaped, and generic computer-use runs, then exposing failed steps through a local trace viewer and redacted shareable exports.

Primary documented web-agent use case

https://github.com/aaronlab/browsertrace#readme

Public reference

https://github.com/aaronlab/browsertrace

Affiliation disclosure

I am affiliated with BrowserTrace: I maintain it under the aaronlab account.

Checklist

• This PR adds exactly one item.
• I added the item to the bottom of the best-fit section.
• The description is factual, neutral, and ends with a period.
• This is directly relevant to web agents, not just AI tooling in general.
• I checked for duplicates before submitting.

Local verification:

• GITHUB_TOKEN=$(gh auth token) npx -y awesome-lint@2.2.3 README.md -> passed.
• /Users/enyuanzhang/.gem/ruby/2.6.0/bin/awesome_bot --allow-dupe --allow-redirect --white-list "https://github.com/steel-dev/awesome-web-agents,https://surf.new,https://openai.com/index/introducing-operator/,https://www.perplexity.ai/comet,https://openai.com/research/webgpt,https://dzone.com/articles/build-ai-browser-agent-llms-playwright-browser-use,https://dev.to/nodeshiftcloud/build-a-browser-use-agent-with-deepseek-a-step-by-step-guide-2n59" README.md -> No issues.
• git diff --check -> clean.