Research Analysis

The Rise of AI-Native Browser Automation

How browser-use went from 0 to 77,000 GitHub stars in 5 months, challenging a decade of testing infrastructure

In October 2024, a small Python project launched on GitHub with a simple premise: what if you could control a browser with plain English? Five months later, browser-use has accumulated nearly 78,000 stars—a growth rate that took Playwright over two years to achieve.

The Numbers

82K
Playwright Stars
5+ years
78K
browser-use Stars
5 months
27K
Stars in Jan 2025
Single month peak
9.2K
Forks
Active development

Star Growth Over Time

Playwright
browser-use

Timeline of Events

December 2019
Playwright Created
Microsoft forks the Puppeteer team to create a cross-browser automation tool
January 2020
Playwright Launch Day
14,000 stars on announcement—massive Hacker News attention
2020 - 2022
Steady Growth Era
Playwright grows at ~2,000 stars/month, reaching 80K
2023 - 2024
Mature Growth Phase
Growth continues at ~500-1K stars/month as Playwright becomes the industry standard
October 31, 2024
browser-use Launches
AI-native browser automation enters the scene
January 2025
Viral Growth
27,000 stars in a single month—unprecedented adoption rate
March 2025
Near Parity
browser-use approaches Playwright's total star count

What Changed?

The timing wasn't coincidental. browser-use launched exactly when LLMs became reliable enough to consistently understand and execute browser actions. It's built on top of Playwright, but abstracts away the complexity entirely.

Traditional Approach (Playwright)

Write selectors, handle waits, manage state, debug flaky tests, maintain scripts as UI changes

AI-Native Approach (browser-use)

"Click the login button, enter my email, and submit the form"—the AI figures out the rest

"This is basically the AI-native Selenium moment—the same disruption Playwright brought to Selenium, browser-use is bringing to Playwright."

— Observation from the growth pattern analysis

Real-World Use Cases

So why are 78,000 developers interested? browser-use solves tasks that were previously either impossible to automate or required significant engineering effort.

Job Application Automation

Upload your resume once, then let an AI agent apply to hundreds of jobs on LinkedIn, Workday portals, and company career pages—filling forms, answering screening questions, and submitting applications while you sleep.

agent.run("Apply to ML Engineer jobs in London, use my resume.pdf")

Automated Shopping & Price Monitoring

Compare prices across Amazon, eBay, and niche retailers. Set up agents to monitor stock levels, alert you when prices drop, or automatically purchase items when they meet your criteria.

agent.run("Find RTX 4090 under $1500, compare 5 stores")

Data Extraction & Research

Scrape competitor pricing, gather lead lists from directories, extract product specs from manufacturer sites, or compile research from multiple sources—all with natural language instructions.

agent.run("Get all YC W24 startups with AI in description")

Appointment & Booking Management

Monitor government appointment slots (visa, DMV), snag restaurant reservations the moment they open, or book recurring appointments automatically. The agent handles CAPTCHAs and login states.

agent.run("Check US visa slots daily, alert if available")

Form Filling & Admin Tasks

Automate expense reports, fill insurance claims, submit compliance forms, or update CRM records across systems that don't have APIs. Perfect for tedious back-office work.

agent.run("Fill expense report from receipts folder")

Social Media & Outreach

Find influencer profiles matching criteria, gather contact info from LinkedIn (respecting ToS), or automate personalized outreach sequences across platforms without API access.

agent.run("Find 50 tech YouTubers with 10K-100K subs")

Quick Start Example

The entire browser-use API fits in your head. Here's a complete working example:

Python example.py
from browser_use import Agent, Browser
from langchain_openai import ChatOpenAI

async def main():
    agent = Agent(
        task="Go to amazon.com, search for 'mechanical keyboard',
              filter by 4+ stars and under $100,
              return top 5 options with prices",
        llm=ChatOpenAI(model="gpt-4o"),
        browser=Browser()
    )
    result = await agent.run()
    print(result)

# That's it. No selectors. No waits. No maintenance.
Why This Matters

The same task in Playwright would require: finding the search input selector, handling dynamic loading, locating filter checkboxes, waiting for results, parsing the product grid, and maintaining all of this when Amazon updates their UI. browser-use reduces this from ~100 lines to 10.

The Contributors

Contributor Commits Role
MagMueller 3,081 Founder, primary maintainer
pirate (Nick Sweeting) 1,810 Known for ArchiveBox
mertunsall 814 Core contributor
gregpr07 471 Co-founder

What This Means

For Test Automation

The industry is shifting from "write scripts that click elements" to "describe what you want to happen." This fundamentally changes who can write automated tests and how quickly test suites can be created.

For Developer Tooling

AI-native tools aren't just incremental improvements—they represent a paradigm shift. The growth rate difference (5 months vs 5 years to similar star counts) suggests developers are hungry for this abstraction level.

For the Testing Ecosystem

Traditional tools won't disappear—browser-use literally runs on Playwright. But the abstraction layer is moving up. The question isn't "Playwright or browser-use" but rather "which level of abstraction do you need?"

Playwright's Sweet Spot

Complex test suites requiring fine-grained control, CI/CD integration, cross-browser matrix testing

browser-use's Sweet Spot

Rapid prototyping, one-off automation tasks, non-technical users, exploratory testing

Looking Ahead

The AI testing revolution is happening faster than most anticipated. While commercial SaaS tools like testRigor, Functionize, and BlinqIO have been exploring this space, browser-use's open-source approach has captured developer mindshare at an unprecedented rate.

The next frontier? Self-healing tests that adapt to UI changes, AI agents that can explore applications and generate tests automatically, and natural language test specifications that non-technical stakeholders can write and understand.

One thing is clear: the 77,000 developers who starred browser-use in five months are voting with their attention. The era of AI-native developer tools has arrived.

Data collected and analyzed from GitHub API • February 2026

View star history at star-history.com