Fetching from the wire…
Public story · 2026-07-01 · high
It swaps DOM selectors for computer vision and already logs 10 million-plus workflow runs, undercutting Playwright rivals like Stagehand.
Why now: Skyvern showed up as one of the week's fastest-growing agent repos just as vision-based and DOM-based browser automation get compared head to head.
Skyvern climbed to roughly 21,500 GitHub stars this week, making it one of the fastest-growing browser automation agents on the platform, per its GitHub repo.
The project already claims more than 10 million executed workflows and sub-300ms response times. It skips the DOM selectors most browser agents rely on. Instead, it reads a page the way a person does, using natural language instructions plus computer vision to click, scroll, and fill in forms.
That matters because DOM selectors are the thing that breaks every time a site ships a redesign. Anyone who's maintained a Playwright suite knows the drill: a class name changes, the suite goes red, someone spends an afternoon rewriting locators. A vision-based agent is betting it can skip that entirely by working off pixels instead of markup.
Skyvern isn't the only one making that bet. Stagehand takes a hybrid approach, still running on Playwright under the hood while adding natural-language steps on top. Skyvern goes further and cuts selectors out of the picture completely.
One caveat: 21,500 stars is a single-source growth signal from GitHub. It's not a benchmark against Stagehand or Playwright on task success rate, cost, or latency at scale. Star counts measure attention, not whether the thing works better in production.
Pixels don't need refactoring the way markup does, so the long-term bet favors Skyvern's approach. What the star count can't tell you is whether it actually beats Stagehand on task success or cost once real teams put it into production. That's the number worth watching next, not the GitHub trend chart.
Each link below shares sources, entities, or timing with this story.
Anthropic uses Playwright / Shared entities / Same source domain / What happened next
Linked by a graph relationship (Anthropic uses Playwright); both cover DOM, GitHub; reported by the same outlet (github.com).
Anthropic uses Playwright / Shared entity: GitHub / Same source domain / Earlier coverage
Linked by a graph relationship (Anthropic uses Playwright); both cover GitHub; reported by the same outlet (github.com).
Anthropic uses Playwright / Shared entity: GitHub / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Anthropic uses Playwright); both cover GitHub; reported by the same outlet (github.com).
Claude Code supports Playwright / Shared entities / Same source domain / Earlier coverage
Linked by a graph relationship (Claude Code supports Playwright); both cover GitHub, Playwright; reported by the same outlet (github.com).
Anthropic uses Playwright / Shared entity: GitHub / Same source domain / What happened next / Tension
Linked by a graph relationship (Anthropic uses Playwright); both cover GitHub; reported by the same outlet (github.com).
Yadda uses Playwright / Shared entities / What happened next
Linked by a graph relationship (Yadda uses Playwright); both cover GitHub, Playwright; picks up the GitHub thread on 2026-08-16.
Claude Code supports Playwright / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Claude Code supports Playwright); both cover DOM, GitHub; reported by the same outlet (github.com).
Anthropic uses Playwright / Shared entity: GitHub / Same source domain / What happened next
Linked by a graph relationship (Anthropic uses Playwright); both cover GitHub; reported by the same outlet (github.com).