What is browser automation?
Software driving a browser in place of a person. Three generations answer to the name, and the newest one reads the page on every run, so a redesign costs you nothing.
Browser automation is software driving a web browser in place of a person: opening pages, clicking, filling and submitting forms, reading what comes back, and repeating that reliably. It began as a testing technique and became the general way to do web work that has no API.
Three quite different generations of tool answer to the name, which is why advice about it contradicts itself. The newest one takes a plain-language instruction and reads the page fresh every run.
What are the three kinds of browser automation?
In rough historical order:
- Code frameworks: Selenium, Puppeteer, Playwright. An engineer writes the steps and the selectors. Deterministic and exact, and it breaks the day the page changes.
- Recorded and visual tools, including RPA platforms. Click through the task once, replay it forever, with the same brittleness and some enterprise governance on top.
- AI browser agents. The instruction is plain language and the agent reads the page each run, so layout changes and judgment calls (“skip the sponsored results”) are handled on the run.
What does browser automation look like in practice?
A weekly supplier price check.
Eleven vendor portals, each with its own login and its own table layout, one number needed from each plus a flag on anything that moved. A code framework does that in eleven scripts you now maintain forever.
A companion does it as one instruction, reads each page fresh, and hands back the eleven numbers with the changes marked. The workflow is at automate vendor price checks, and the same machinery runs monitor competitor prices.
Why browser automation breaks
Four causes account for most of it.
Markup changes, and selector-based automation dies silently. Logins get harder, and unattended scripts stall at the wall. Bot defenses classify automation and start serving CAPTCHAs. Dynamic pages load content after the script looked, which produces empty results rather than errors.
An agent reading the rendered page each run absorbs the first and the last of those. Terms of service, rate limits and personal-data rules apply whichever generation you use.
The choice between them comes down to who fixes it when portal seven redesigns, which is the argument at AI for repetitive browser work.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents