Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for operators who want persistent browser automation on their own box instead of keeping an AI browser session alive on a personal machine.
Who should use it
Who should skip it
Skip browser-use/bux if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
browser-use/bux is tracked by RepoRadar as a browser automation agent in the Developer Workflow section. It was first seen on 2026-06-30 and last updated on 2026-06-30. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for browser-use/bux are workflow potential (9.6) and open-source/build quality (8.4), while setup ease (6.4) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned browser-use/bux a composite score of 8.1 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
It keeps a real logged-in browser on a remote box, so first rollout should stay on test accounts or tightly scoped workspaces with least-privilege access; The default path depends on Browser Use Cloud credentials and can add remote messaging control, so teams should review the exposure window before using it for production browsing.