Review economics
vercel-labs/agent-browser
Read from the 100 most recently merged pull requests ·
Not enough merged pull requests on both sides yet to compare how they land in review.
≥1%
Attributed
a floor
2
Attributed PRs
98
Other PRs
100
Read
Attributed — the latest 2
The rest — the latest 5
#1648 docs: add Remote Agent Browser provider guide
2 reviews · 10h to merge
#1641 fix(doctor): stop hanging on the Chrome version query
1 reviews · 2h to merge
#1637 test(native): raise parity action timeout to 60s
1 reviews · 28h to merge
#1628 Prepare v0.33.2 release
1 reviews · 1h to merge
#1626 feat(stream): configurable screencast quality and frame size
1 reviews · 6h to merge
How this was measured
1% of merged commits carry agent attribution — a floor, not the share; tools that only complete code inline leave no commit trail, so the unattributed side includes AI-assisted work; reads 100 of 578 merged PRs — the rest have not been analyzed yet.
Detected: GitHub Copilot coding agent, Claude Code.
“Attributed” means a commit carried an agent’s signature — a co-author trailer, an agent commit identity, or an agent bot account. Tools that only complete code inline leave no such mark, so the other column is “rest”, not “human-written”. Full method and its limits
The badge reads this repo’s current report, so it follows the number.
Tell me when this moves
We re-read vercel-labs/agent-browser weekly and email only when the number changes materially.
Read your own repos
This one is public. For a private repo, run the same read locally through your own GitHub credentials — nothing is installed and nothing is sent to us.
npx @ambera/review-taxWant this continuously on vercel-labs/agent-browser — each pull request paired to the task it came from, and the work graded from its review loop rather than its diff size? Claim this repo in Forge
Browse every repo people have read · Read a different repository