Joined February 2018
- Tweets 286
- Following 155
- Followers 983
- Likes 316
29 Photos and videos
Jun 12
See how our browser agent fills out a contact form from a single sentence.
Your AI assistant navigates real sites like a person: reads the page, fills fields, picks the right dropdown, clears the Cloudflare check, submits. Powered by our MCP server on a real Chrome session. No selectors, no scripts.
Watch it in action. Docs in the replies.
1
7
273
Jun 12
1
102
Jun 11
Same Amazon product page. Same prompt in Claude.
Browserless MCP: 35s.
Browserbase MCP: 105s.
3x faster on one page. Negligible until your agent makes that call a thousand times.
If your agent scrapes the web all day, Browserless MCP is built for you.
Setup below.
1
1
5
353
Jun 11
133
Jun 2
You're already logged into the sites you want to automate. Your automation should be too.
The new Browserless CLI reads the login from your own Chrome, Edge, or Brave and turns it into a cloud profile. Set it up once with a single command, and every session after starts already signed in.
Learn more below.
1
2
3
234
Jun 1
We started as “headless Chrome in the cloud.” That’s still in there, but it's not the whole story.
Browsers as a Service is still the core. Web APIs are the LLM-era layer. The MCP server lets your AI agent drive a real Chrome session, state and all. And all of it runs self-hosted on your hardware if you need it.
Same stealth infra underneath everything. All on the same bill.
Which one didn't you know we shipped?
1
2
206
May 28
Browserless is now on the Devin MCP marketplace.
Your AI engineer can browse the live web, pull real data, and automate browser tasks.
1
1
2
223
May 20
You pay each time you have to log in on each browser session. Scrapers, agents, internal automation. The login bill adds up.
That’s why we just shipped Authenticated Profiles.
Log in once on Browserless. Reuse that saved login across unlimited parallel sessions.
3
1
1
227
May 12
CAPTCHAs are the #1 reason Browser Use agents fail in production.
Run it on Browserless and that just stops being a problem. Two parameters. Free tier included. Same engine running production automation for thousands of companies → na2.hubs.ly/H05rGDZ0
2
2
269
Apr 15
Scrape any URL. One endpoint. Zero configuration.
Introducing Smart Scrape API.
The API finds the fastest path to your content, and you only pay for the strategy that works.
1
2
6
340
Apr 15
How it escalates:
→ Direct fetch first (cheapest)
→ Proxy fallback if blocked
→ Headless Chrome for JS-rendered pages
→ Automatic CAPTCHA solving when needed
Simple pages stay cheap. Tough pages get through.
1
184
Apr 15
One request, multiple formats: HTML, Markdown, links, screenshot, PDF.
We've solved millions of CAPTCHAs over 8 years. Smart Scrape puts all of it behind one endpoint.
Try it: browserless.io/account/rest-…
1
161
Mar 17
This is a big deal for browser automation infrastructure. ARM64 Chrome means lower compute costs, fewer Chromium edge cases, and way more flexibility in where you run headless browsers. We're already exploring what this unlocks for Browserless users.
Mar 17
Google is finally bringing Chrome to ARM64 Linux devices. Very exciting for two reasons: better automation capabilities — and much cheaper.
It also means you’ll be able to do a lot more with @browserless and Raspberry Pi. Stuff like:
- Being able to run on many different machines, like AWS arm64 instances.
- Watch and record sites that have mp4 video files.
- Run tests on a variety of new machine types if you’re unit-testing.
Another big plus is that you won’t have to deal with Chromium-related edge cases and automation setbacks like fingerprint differences, missing codecs, etc.
Raspberry Pi is already very popular with home automation tinkerers, so I expect to see some really cool use cases in the near future. Will definitely be keeping an eye out.
4
500
Jan 20
Browserless crossed 12,000 GitHub stars last month.
8 years of commits. 77 contributors. Almost 1,000 forks. Thousands of production environments we will never see.
Here is what open source taught us about building a company:
1
1
9
959
Jan 20
The fastest way to learn is to let users tell you what you missed.
Most feature requests are noise. The ones that show up three times from three users are signal.
1
496
Jan 20
Thank you to everyone who contributed code, filed an issue, or answered a question in Discord.
These lessons came from you.
Now back to building.
398