Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams building browser agents or evidence-collection workflows that need visible, lease-scoped Chrome state and a controlled human handoff path instead of one-shot headless fetches.
Who should use it
Who should skip it
Avoid running energypantry/agent-browser-runtime in production until you have reviewed its permissions, data-access scope, and failure modes in a sandbox.
About this signal
energypantry/agent-browser-runtime is tracked by RepoRadar as a browser runtime in the Browser Agents section. It was first seen on 2026-06-30 and last updated on 2026-06-30. The current verdict is 'worth watch' with a Silver tier and advanced setup difficulty. Across RepoRadar's eight signals, energypantry/agent-browser-runtime is strongest on workflow potential (8.7) and open-source/build quality (8.4) and weakest on setup ease (4.2) — a profile worth weighing against your own priorities. 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 energypantry/agent-browser-runtime a composite score of 7.9 out of 10, placing it in the Silver 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 'medium' 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 is built around persistent Chrome profiles, session reuse, and login-state probing, so first evaluation should use disposable accounts and a tightly scoped internal allowlist; The runtime ships humanized pacing, extractors, and manual challenge handoff, so review legal, platform, and compliance boundaries before pointing it at third-party sites.