Add BrowserTrace#136
Closed
aaronlab wants to merge 1 commit into
Closed
Conversation
Author
|
Local verification update: |
0f3876b to
f2d652b
Compare
Owner
|
Thanks for sharing BrowserTrace! It looks handy, but it's framed primarily around Browser Use agents rather than Playwright, and it's quite early-stage. Feel free to resubmit once it's more clearly Playwright-focused with broader adoption. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds BrowserTrace to the utilities list.
BrowserTrace is a local trace viewer for Playwright scripts where an LLM or browser agent is part of the control loop. It records screenshots, URLs, actions, model input/output, errors, and shareable HTML exports so failed Playwright + LLM runs are easier to debug.
Notes:
I also ran the repo's
npx -y awesome-lint README.mdcommand locally; it failed on an environment-levelAwesome list must reside in a valid git repositorymessage rather than this entry, so I expect the GitHub CI context to be the meaningful check.