BrowserTrace v0.1.19: replay and compare Browser Use failures locally #6
Replies: 33 comments
-
|
Roadmap tracking is now open here: https://github.com/aaronlab/browsertrace/milestone/1 Current v0.2 launch follow-up items:
|
Beta Was this translation helpful? Give feedback.
-
|
Added a value-first walkthrough for people who want the debugging workflow before trying the repo: https://aaronlab.github.io/browsertrace/debug-browser-agent-failure.html It shows the failure pattern, the local trace commands, and the questions to ask at the first red step. |
Beta Was this translation helpful? Give feedback.
-
|
Integration feedback is now structured. If you are using Browser Use, Stagehand, Playwright + LLM scripts, Skyvern, or a custom computer-use agent, please open an integration request here: https://github.com/aaronlab/browsertrace/issues/new?template=integration_request.yml The form asks which stack you use, what failure current logs do not explain, which hooks BrowserTrace should wrap, and whether you can test a preview adapter. |
Beta Was this translation helpful? Give feedback.
-
|
Launch update: the public sharing assets are now ready. Useful links:
Prepared launch materials now include Day 1 social posts, Show HN notes, targeted Browser Use / Stagehand / Playwright / Skyvern community drafts, Product Hunt listing copy, and a Chinese long-form technical post. The most useful feedback is still workflow-specific: if you build browser agents, what state do you wish your trace captured at failure time? Screenshots, DOM/extracted text, selectors, model input/output, workflow state, retries, or something else? |
Beta Was this translation helpful? Give feedback.
-
|
Release update: BrowserTrace v0.1.2 is now available. Release: What changed:
The next useful feedback is still workflow-specific: for Browser Use, Stagehand, Skyvern, Playwright + LLM, or custom computer-use agents, which failure artifacts should BrowserTrace capture first? |
Beta Was this translation helpful? Give feedback.
-
|
Release update: BrowserTrace v0.1.7 is now available. Release: New since the earlier launch discussion:
The most useful feedback is still concrete failure context: for Browser Use, Stagehand, Skyvern, Playwright + LLM, or custom computer-use agents, what did your logs or traces miss when the run failed? |
Beta Was this translation helpful? Give feedback.
-
|
Release update: BrowserTrace v0.1.8 is now available. Release: New in this release:
Public sharing commands: browsertrace export <run_id> --redact -o public.html
browsertrace export <run_id> --redact --redact-screenshots -o public.htmlFeedback wanted: when you share browser-agent traces publicly, what else needs redaction besides prompt/model I/O and screenshots? |
Beta Was this translation helpful? Give feedback.
-
|
Release update: BrowserTrace v0.1.9 is now available. Release: New in this release:
Public sharing command: browsertrace export <run_id> --redact --redact-screenshots --redact-urls -o public.htmlFeedback wanted: what else should a browser-agent trace be able to redact before sharing publicly? |
Beta Was this translation helpful? Give feedback.
-
|
Launch kit update for
Current launch stance is unchanged: ask for real browser-agent debugging workflow feedback, not stars, upvotes, or vote swaps. |
Beta Was this translation helpful? Give feedback.
-
|
Launch log update:
No paid stars, fake engagement, vote swaps, or direct star asks. |
Beta Was this translation helpful? Give feedback.
-
|
Launch log update:
Search indexing is a long-tail discovery channel only. No fake traffic, click farms, doorway pages, or keyword stuffing. |
Beta Was this translation helpful? Give feedback.
-
|
Launch log update: PyPI is still the main install-conversion blocker, but the release now has a verified no-install uvx --from "browsertrace[ui] @ git+https://github.com/aaronlab/browsertrace@v0.1.10" browsertrace demo
uvx --from "browsertrace[ui] @ git+https://github.com/aaronlab/browsertrace@v0.1.10" browsertrace list
uvx --from "browsertrace[ui] @ git+https://github.com/aaronlab/browsertrace@v0.1.10" browsertraceVerified locally with an isolated This is only a bridge until PyPI Trusted Publisher is configured. The launch goal remains unchanged: get real feedback from people debugging Browser Use, Stagehand, Skyvern, Playwright + LLM, and custom computer-use agent failures. No paid stars, fake engagement, vote swaps, or direct star asks. |
Beta Was this translation helpful? Give feedback.
-
|
v0.1.11 is now published and verified. The main first-run addition is uvx --from "browsertrace[ui] @ git+https://github.com/aaronlab/browsertrace@v0.1.11" browsertrace doctor
uvx --from "browsertrace[ui] @ git+https://github.com/aaronlab/browsertrace@v0.1.11" browsertrace demo
uvx --from "browsertrace[ui] @ git+https://github.com/aaronlab/browsertrace@v0.1.11" browsertrace list
uvx --from "browsertrace[ui] @ git+https://github.com/aaronlab/browsertrace@v0.1.11" browsertraceVerified from the GitHub tag with isolated PyPI is still pending owner-side Trusted Publisher setup, so GitHub install/uvx remains the public trial path for now. |
Beta Was this translation helpful? Give feedback.
-
|
Computer-use update for custom browser-agent builders:
The example records a generic observe -> decide -> act loop, then marks the model-selected checkout click as the failed step. I am especially looking for feedback on which fields custom computer-use agents should capture by default: observation text, screenshot, URL, action label, model input/output, selector, retries, latency, or redaction policy. |
Beta Was this translation helpful? Give feedback.
-
|
Launch/contributor update 2026-05-09:
Still asking for browser-agent debugging workflow feedback only. No star asks, upvote asks, vote swaps, or artificial engagement. |
Beta Was this translation helpful? Give feedback.
-
|
Launch/contributor update:
Latest verified local suite: Still looking for workflow feedback from people debugging Browser Use, Stagehand, Skyvern, Playwright + LLM, or custom computer-use agents. The most useful feedback is which browser state or model decision context was missing when a real run failed. |
Beta Was this translation helpful? Give feedback.
-
|
Launch/contributor update 2026-05-10:
Still looking for concrete workflow feedback from people debugging Browser Use, Stagehand, Skyvern, Playwright + LLM, or custom computer-use agents: what browser state or model-decision context did your logs miss at the failed step? |
Beta Was this translation helpful? Give feedback.
-
|
Launch/discovery update 2026-05-10: High-fit external discovery PRs currently open for BrowserTrace:
These are framed as browser-agent debugging / observability / harness-engineering entries, not as generic AI promotion. Current status: open, no maintainer change requests from us to handle right now. Current small contribution path: #223. Current repo audit: 3 stars / 5 forks / 0 watchers, so the 1000-star goal is still incomplete. Remaining owner-side conversion blockers are PyPI Trusted Publisher, GitHub social preview upload, and pinning BrowserTrace on the No paid stars, fake engagement, vote swaps, star asks, or upvote asks. The useful ask remains workflow feedback from people debugging Browser Use, Stagehand, Skyvern, Playwright + LLM, or custom computer-use agent failures. |
Beta Was this translation helpful? Give feedback.
-
|
Launch/discovery status update (2026-05-10):
Current repo status from GitHub: 3 stars, 5 forks. Still far from the 1000-star goal, so the next work remains legitimate discovery, useful docs, contributor care, and owner-only launch actions. No fake engagement, vote swaps, or star asks. |
Beta Was this translation helpful? Give feedback.
-
|
v0.1.15 is now published with Browser Use run-hook support. Release: https://github.com/aaronlab/browsertrace/releases/tag/v0.1.15 What changed:
Verification:
No fake engagement or star asks. Current growth blockers remain owner-only: PyPI Trusted Publisher, GitHub social preview upload, profile pin, E2B CLA, and real owner social/community posts. |
Beta Was this translation helpful? Give feedback.
-
Current quick trial path: uvx --from "browsertrace[ui]" browsertrace doctor
uvx --from "browsertrace[ui]" browsertrace demo
uvx --from "browsertrace[ui]" browsertrace list
uvx --from "browsertrace[ui]" browsertracePersistent install: pip install "browsertrace[ui]"Release: https://github.com/aaronlab/browsertrace/releases/tag/v0.1.17 The main discussion body has been refreshed to the current PyPI install path and release assets. Still looking for workflow feedback from people debugging Browser Use, Stagehand, Skyvern, Playwright + LLM, or custom computer-use failures. No star/upvote asks. |
Beta Was this translation helpful? Give feedback.
-
|
Contributor queue update (2026-05-11):
If you want to help, #248 is intentionally docs-only and narrow. Please include the exact commands you ran when opening a PR. No stars/upvotes requested; concrete workflow and docs feedback is the useful signal. |
Beta Was this translation helpful? Give feedback.
-
|
Launch/discovery update (2026-05-12): BrowserTrace now has a focused failure-patterns page for people evaluating whether it matches their browser-agent debugging workflow. Failure patterns page: It summarizes the concrete cases the project is designed around:
Current quick trial path remains: uvx --from "browsertrace[ui]" browsertrace doctor
uvx --from "browsertrace[ui]" browsertrace demo
uvx --from "browsertrace[ui]" browsertraceIf you build browser agents, the feedback I need most is: which failure pattern do you hit most often, and what trace evidence is still missing from your current workflow? No stars/upvotes ask here; workflow feedback is the useful signal. |
Beta Was this translation helpful? Give feedback.
-
|
Contributor queue update (2026-05-12): The current open good-first docs tasks are:
Both are intentionally narrow docs-only tasks for first-time contributors. Please comment on the issue before starting so maintainers can treat it as claimed and avoid duplicate work. Current repo audit remains 3 stars / 18 forks / 0 watchers, so the 1000-star goal is still incomplete. No stars/upvotes requested; workflow feedback and focused docs improvements are the useful signal. |
Beta Was this translation helpful? Give feedback.
-
|
Contributor queue refresh (2026-05-12):
Please keep first PRs small, scoped, and verified with |
Beta Was this translation helpful? Give feedback.
-
|
Contributor queue refresh (2026-05-12):
Please comment on the issue before starting so maintainers can mark it claimed and avoid duplicate work. Keep first PRs small, scoped, and verified with Current repo audit remains 3 stars / 18 forks / 0 watchers, so the 1000-star goal is still incomplete. No stars/upvotes requested; concrete workflow feedback and focused docs improvements are the useful signal. |
Beta Was this translation helpful? Give feedback.
-
|
Contributor queue refresh (2026-05-12):
Please comment on the open issue before starting so maintainers can avoid duplicate work. Keep first PRs small, scoped, and verified with Current repo audit remains 3 stars / 21 forks / 0 watchers, so the 1000-star goal is still incomplete. No stars/upvotes requested; concrete workflow feedback and focused docs improvements are the useful signal. |
Beta Was this translation helpful? Give feedback.
-
|
Contributor queue refresh (2026-05-12):
Please comment on the open issue before starting so maintainers can avoid duplicate work. Keep first PRs small, scoped, and verified with Current repo audit remains 3 stars / 21 forks / 0 watchers, so the 1000-star goal is still incomplete. No stars/upvotes requested; concrete workflow feedback and focused docs improvements are the useful signal. |
Beta Was this translation helpful? Give feedback.
-
|
Contributor queue refresh (2026-05-12):
Please comment on the open issue before starting so maintainers can avoid duplicate work. Keep first PRs small, scoped, and verified with git diff --check plus the focused metadata test when applicable. Current repo audit remains 3 stars / 21 forks / 0 watchers, so the 1000-star goal is still incomplete. No stars/upvotes requested; concrete workflow feedback and focused docs improvements are the useful signal. |
Beta Was this translation helpful? Give feedback.
-
|
Contributor queue refresh (2026-05-13):
Current pinned issues are #3 for launch/workflow feedback, #11 for Browser Use adapter feedback, and #371 for the open good-first contribution path. Please comment on #371 before starting so maintainers can avoid duplicate work. Keep the PR docs-only, run Current repo audit remains 3 stars / 21 forks / 0 watchers, so the 1000-star goal is still incomplete. No stars/upvotes requested; concrete workflow feedback and focused docs improvements are the useful signal. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
BrowserTrace v0.1.19 is published on PyPI and ready for first Browser Use users.
BrowserTrace is a local replay debugger for Browser Use failures. It records each run as a timeline with screenshot, URL, action, model input/output, status, and error, so the failed browser step is easier to inspect than a log stream alone.
The current demo leads with a concrete Browser Use failure: the agent tries to upload
file:///tmp/browsertrace-report.html, navigates to the local file path instead, and the upload preview never appears.v0.1.19 also adds explicit failed-vs-good comparison:
When a failed Browser Use run has a known-good baseline, the command reports the first divergent action, URL, status, or error before you open the local UI.
Browser Use is the primary path. Stagehand, Skyvern, Playwright + LLM scripts, and custom computer-use agents remain supported as secondary integrations.
Concrete Browser Use failure shapes covered in the current docs include local HTML upload navigation, new-tab desync, remote CDP hangs, and icon-only target mismatch.
Zero-install live demo:
https://aaronlab.github.io/browsertrace/
Try it locally in 60 seconds from PyPI:
Persistent install:
pip install "browsertrace[ui]" browsertrace doctor browsertrace demo browsertraceThen open http://127.0.0.1:3000 and inspect the failed demo run.
browsertrace doctorworks before any trace database exists, so it is the first command to run if setup fails.Public-safe export:
--publicomits prompt/model I/O, screenshots, and URLs from the standalone HTML export. Individual redaction flags remain available when you want to keep some fields visible.Useful links:
Feedback wanted from Browser Use builders:
Please do not post private prompts, screenshots, credentials, cookies, tokens, customer data, or private trace data in public issues/discussions. Use
browsertrace export --publicbefore sharing a real trace publicly, and use the Security Policy for security-sensitive reports or changes.No star asks, upvote asks, vote swaps, or artificial engagement. Workflow feedback from real Browser Use and browser-agent builders is the useful thing.
Beta Was this translation helpful? Give feedback.
All reactions