Updated
Browser Automation for Agents · for Next.js

Browser Automation for Agents for Next.js: what 12 makers' products chose

Among 12 makers' products built with Next.js that we know the browser automation for agents of, Browserbase leads: 7 of them (58%). Next come Browser Use (4) and Kernel (1).

Browser infrastructure or agent logic. Browser infrastructure runs the headless browsers for you, with sessions, proxies and recordings, and your code decides what to do. Agent libraries supply the model-driven logic that decides where to click, and can run on your own browser or a hosted one. Underneath both sits a plain automation library, where you script every step yourself.

What makers on Next.js chose

OptionNext.js productsAll makers
BrowserbaseHosted browsers7 (58%)55%
Browser UseAgent library4 (33%)41%
KernelHosted browsers1 (8%)3%

Live makers' products with a source for both: that they're built with Next.js, and what they use for browser automation for agents. A product using two options counts in both; not market share. "All makers" is the option's share among every maker's product that made this decision.

Which to pick, by situation

Browserbase

Hosted browsers

7 Next.js products here (58%).

In Replit

Best forRunning many headless browsers in the cloud with session recordings, proxies and captcha handling.

Trade-offHosted only, billed by browser time.

“Browserbase has been the easiest platform to give Karen the power to automate form filling, allowing us to not worry about Chrome instances in the cloud and focus on workflows”

Next.js products on Browserbase
AirKaren
AirKarenAI that fights customer service for you

“Browserbase has been the easiest platform to give Karen the power to automate form filling, allowing us to not worry about Chrome instances in the cloud and focus on workflows”

Browser Automation for AgentsMaker says so · source ↗

All of Browserbase: who uses it, alternatives →

Browser Use

Agent library

4 Next.js products here (33%).

Best forGiving a model a browser and a goal in a few lines of Python, and letting it work out the clicks.

Trade-offEvery step costs model calls and time, and results vary run to run.

“Browser use are our great supporters and lets us do automated browser testing”

Next.js products on Browser Use
Gedd.it
Gedd.itFind Verified Promo Codes for Products You Want

“Gedd.it wouldn't be possible without Browser Use!”

Browser Automation for AgentsMaker says so · source ↗
Superset
SupersetA desktop workspace for running many coding agents (Claude Code, Codex, OpenCode and oth…

“Browser use are our great supporters and lets us do automated browser testing”

Browser Automation for AgentsMaker says so · source ↗

All of Browser Use: who uses it, alternatives →

Also chosen, and not seen yet

Fewer Next.js products here: Kernel (1).

Real options for browser automation for agents not seen among these Next.js products yet: Steel, Stagehand, Playwright, Puppeteer.

Getting browser automation for agents right

Use an API if one exists; browser agents are slow, cost tokens on every step and break when pages change. Script the steps you know with plain Playwright and let the model handle only the parts that vary. Develop against a local browser, and move to hosted browsers when you need many parallel sessions or run from servers that sites block.

  • Letting the model decide every click on a flow that never changes, paying tokens and latency for something a script does reliably.
  • Running agents with a user's logged-in session and no limits on what they may submit, buy or delete.
  • Ignoring a site's terms and bot protection, then building a feature that breaks the week it gets blocked.

The rest of the Next.js stack

What makers' Next.js products chose for their other decisions, the most common pick for each:

Questions

What do most Next.js apps use for browser automation for agents?

Among 12 makers' products built with Next.js that we know the browser automation for agents of, Browserbase leads: 7 of them (58%). Next come Browser Use (4) and Kernel (1).

How this is counted: a product is on Next.js when a live-product source says so (the maker, its website, a customer story or a subprocessor list), and the same for its browser automation for agents. How evidence is collected.