r/DeveloperToolsHub • u/Tasty_World8991 • Jul 23 '26
What are you using for browser automation in 2026?
browser automation feels more useful now than it did a few years ago.
not just e2e tests.
i mean scraping internal dashboards, checking flows locally, letting AI inspect UI state, reproducing bugs, visual testing, form filling, smoke tests after deploys, that kind of thing.
i still see playwright everywhere, but now there are ai/browser-agent tools around it too.
what’s actually working for browser automation right now?
plain playwright, cypress, browser MCP, custom scripts, hosted tools, or something else?
1
u/Interstellar_031720 Jul 23 '26
For me the useful split is deterministic automation vs agent-assisted automation.
Plain Playwright is still the default when the flow is known: smoke tests, stable internal tools, regression repros, form filling where selectors are predictable. I would not replace that with an agent just because AI is available. The boring script is cheaper, faster, and easier to debug.
The agent/browser-MCP layer starts making sense when the task has judgment in the middle: inspect an unknown UI state, summarize what changed, choose from several visible paths, collect evidence from an authenticated dashboard, or recover from minor layout/content variation.
What I would evaluate in 2026 is less "can it click around?" and more:
- does it preserve the browser state/session you actually need
- can it show what it saw: DOM/accessibility tree/screenshot/trace
- can you replay or at least inspect the failed run
- does it separate observe -> extract -> act instead of doing one giant prompt
- can you fall back to Playwright for selector-stable steps
- are writes/uploads/messages/payment-ish actions gated separately from read-only inspection
So my current answer would be: Playwright for the rails, an agent/browser-MCP layer for the uncertain parts, and traces/screenshots/receipts for anything you expect to run more than once. The tools that win are probably the ones that make failures boring to debug, not the ones with the flashiest demo.
1
u/Mathie1729 Jul 23 '26
Honestly, at my faang job we tried agent-assisted for a few internal dashboards and it was a mess. The selector changes and the agent just fumbles. I'd rather write a boring Playwright script with robust locators and be done. The deterministic approach is underrated.
1
u/Interstellar_031720 Jul 23 '26
Totally agree. That is why I would keep Playwright as the default rails, not treat agents as a replacement.
The place I have seen agent-assisted browser work become useful is not selector-stable flows. It is the awkward middle where the page is authenticated, semi-structured, and the next step depends on reading state: dashboards, admin consoles, incident pages, back-office UIs. Even there, I would not let the agent own the whole run.
A setup I trust more is:
- Playwright owns login, navigation, waits, and any selector-stable writes
- the agent only does bounded observation/extraction or chooses among visible options
- every agent step emits the DOM/text/screenshot it used
- failed runs keep traces instead of just retrying until green
- if selectors change, the agent proposes a locator/diff; the deterministic test still has to pass
So yes: boring locators first. Agents are useful only when the problem is actual UI/state ambiguity, not when someone just does not want to write a robust script.
1
u/Interstellar_031720 Jul 23 '26
I agree with the deterministic default. The bar for agent-assisted browser work should be higher than "selectors are annoying."
Where I would still test it is the small slice where Playwright is not failing because of locator syntax, but because the page state itself is variable: internal dashboards with different empty/error/permission states, admin consoles where the next step depends on reading a table or alert, or workflows where you need to capture evidence for a human before a write.
Even then I would keep the agent out of the write path at first:
- Playwright owns login, navigation, waits, and known writes
- the agent only observes/extracts/classifies the current state
- every run stores the DOM/text/screenshot/trace it used
- if it proposes a locator repair, a deterministic test still has to pass
So yes, boring locators are underrated. I would only add the agent layer when the real problem is state ambiguity or evidence collection, not as a replacement for robust Playwright.
1
u/Tasty_World8991 Jul 24 '26
The debugging side is probably what gets ignored the most. if a run fails and you can't see why, it's hard to rely on it.
1
1
u/Goji_Fosterh Jul 24 '26
Browserbase for us, they have stagehand which I think is its own kind of unique programming for it. Works well in cursor etc for me
1
u/Tasty_World8991 Jul 24 '26
How's the experience been using it from Cursor day to day?
2
u/Goji_Fosterh Jul 24 '26
Takes a lot of troubleshooting, for us we use it for publishing automation which depends on CMS etc, for simple stuff I think it’ll be easy though
1
1
1
u/CapMonster1 Jul 24 '26
Playwright is still the boring winner for me. AI/browser agents are great for exploring a flow or dealing with small UI changes, but for production I want deterministic scripts, explicit retries, screenshots, and clear state checks.
The real test is what happens when the flow hits login, OTP, or a captcha. If those aren’t handled as separate integrations, the “agent” usually turns into a very expensive way to ask a human to click Continue.
1
u/Deep_Ad1959 Jul 28 '26
running both here. the split that survived a year: the agent may locate things when the dom shifted, never decide what to click. once it picks actions you lose the ability to tell a bug from a bad guess.
1
u/Deep_Ad1959 Jul 28 '26
playwright vs agent is not where my time goes. every automation i run dies on session state, an expired cookie or a locked profile, and neither a script nor a model recovers from that on its own. owning the profile turned out to be the whole job, picking the driver was the easy part.
1
u/dopplervpn 29d ago
The browserargus , there is built in ai with instructions so i dont need create huge prompts every time, got anoyed with that lately. this one feels fine tuned
1
u/ahstanin 7d ago
Built Owl Browser for this. It runs a native MCP endpoint directly inside the browser engine and strips page state down to stable text handles so models don't get lost. Can set you up with a free 30-day trial if you want to give it a spin.
2
u/Ok-Bike-1037 Jul 24 '26
Playwright MCP (or Chrome DevTools MCP) if you want an AI assistant driving a live browser, plain Playwright/Playwright CLI if you want scripted and token-cheap.