They all click now. Not all of them click on your machine.
Where each approach stops.
| Capability | Aera | AI chat tools | Scripts (Puppeteer) | AI extensions |
|---|---|---|---|---|
| Executes on real websites | ||||
| Plain language, no code | No | |||
| Runs on a schedule | ◐ | |||
| Unattended runs happen on your machine, in your session | ◐ | No | ◐ | |
| Keeps running with the browser closed | No | |||
| Reads the page instead of a stored selector | No | |||
| Handles logins & sessions | ◐ | |||
| Your daily-driver browser | No | No | ||
| MCP for your dev tools | No | No |
◐ = possible with significant setup or limitations
The honest version.
Every tool below is good at something. Here's where each one stops, and where Aera keeps going.
Their cloud browser does not sign in. Their local runs need their app open.
ChatGPT drives real websites and runs recurring scheduled tasks. OpenAI's cloud browser works on public pages and does not sign in to sites for you; the ChatGPT desktop app runs scheduled tasks on your machine as long as the computer is on and the app is running, and its built-in browser uses a profile separate from your regular browser. Aera does the same class of work in the Chromium profile you are already signed into, on your machine.
Fair is fair: Use chat tools when the work is writing and reasoning, or when you would rather a rented cloud machine did the clicking than your own.
They're code. Aera is a sentence.
Test frameworks need scripts, selectors, and CI to babysit. Aera reads the page on every run, so a renamed div is not automatically fatal, and there is nothing to deploy.
Fair is fair: Use them for deterministic test suites in CI, and anywhere the same result every time matters more than reading a page.
They're infrastructure. Aera is your browser.
Headless services run backend jobs in someone else's cloud, with your credentials. Aera runs on your machine, in your sessions, in a browser you also use all day.
Fair is fair: Use them for high-volume scraping pipelines at backend scale.
They stop when the window does.
The strongest extensions now schedule recurring browser tasks: Claude in Chrome has done that since November 2025. They keep working only while Chrome is open, because an extension cannot outlive its browser. Aera's scheduler is a separate service on your machine, so a task fires with the browser closed, and files, in-browser code execution and MCP are native rather than bolted on.
Fair is fair: Use an extension if you want an agent inside the browser you already have and you are content for it to work only while that window is open.
Still weighing it? Read the FAQ or see real use cases.
Stop browsing. Start delegating.
Download Aera and put an agent to work in your browser today.