BrowserWorker

Remotely control real Chrome browsers with JSON API

Productivity

Developer Tools

No-Code

Visit WebsiteSee on Product Hunt

Hey Product Hunt 👋 I started building BrowserWorker after hitting the same wall over and over: I needed to automate tasks that involved logging into sites and staying logged in — posting content, filling forms, pulling data from platforms that don't offer (or heavily restrict) API access. My first instinct was the usual path: Playwright, Puppeteer, headless Chrome with stealth plugins. It worked... until it didn't. The moment sites had any real bot detection (Cloudflare, etc.), the automation got flagged, even with anti-detection tweaks. I kept fighting fingerprinting instead of actually building what I wanted to build. At some point I asked a simpler question: what if the "bot" was just... a real browser? Not a spoofed one — an actual Chrome session, logged in normally, doing the same clicks and typing a human would do. That's the core idea behind BrowserWorker: a Chrome extension turns your real browser into a "worker," and you control it remotely via simple JSON actions (open tab, fill field, click) — sent through an API, so it plugs directly into tools like n8n, or any workflow that can make an HTTP request. The approach evolved a lot along the way — early versions tried to be too clever (custom protocols, complex session management), but the simplest version — plain JSON actions + a real logged-in browser — ended up being both the most reliable and the easiest for people to actually use. Would love feedback on: What other actions/integrations you'd want supported Use cases beyond what I've built for so far Anything that feels missing or confusing in the current API/playground Happy to answer anything about how it works under the hood!