Add BrowserTrace to browser interaction tools#30
Open
aaronlab wants to merge 1 commit into
Open
Conversation
|
I found missing media metadata and/or repo-managed submitter metadata that should be written back to the PR branch. I can't push directly to forked PR branches, but you can generate the same changes locally with:\n\n |
11 tasks
Author
|
Updated this PR branch with the generated BrowserTrace metadata requested by the enrichment workflow. Local verification:
The latest Enrich Tool Assets run is passing: https://github.com/bradvin/agentfirst.directory/actions/runs/25617262079 |
063aff3 to
8f107ed
Compare
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
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 Browser Automation category.
BrowserTrace is an open-source local debugger for AI browser-agent runs. It records failed Browser Use, Stagehand, Skyvern, Playwright + LLM, and custom computer-use runs as step timelines with screenshots, URLs, actions, model I/O, status, errors, and public-safe HTML exports.
I kept the listing narrow because this directory has a strict agent-first bar. If this reads as adjacent devtooling rather than agent-first browser tooling, I am happy to adjust or close it.
Validation run locally:
npm test-> 28 passednpm run validate:content-> Content validation passed for 13 categories and 24 toolsgit diff --check-> clean