BrowserBook is an AI-powered IDE for building fast, reliable browser automations. It pairs a Jupyter-style notebook with a context-aware AI coding assistant and an inline browser, enabling developers to write, test, and debug automations all in one place. With built-in auth management, data extraction, screenshot tools, and API deployment, you can go from idea to production-ready automation in minutes, not hours.
Hey Product Hunt! 👋 I’m Chris, co-founder of BrowserBook here with teammates Jorrie and Evan.
We’re excited to share BrowserBook, an AI-powered IDE for building reliable, deterministic browser automations. It combines a notebook-style interface, an inline browser, and a context-aware coding assistant to help developers write, run, and iterate on Playwright scripts faster with built-in tools for screenshots, data extraction, and managed auth.
Why we built this Jorrie and I started a healthcare automation company last summer, where we spent lots of time building back-office workflows (think insurance followup, medical coding, etc.) with custom browser agents. During this time, we ran into four major issues with browser agents:
💰 They’re expensive - we burned through tokens with all the workflow context we needed to provide 🐢 They’re slow - all that context let to super high latency on each request 😬 They’re unreliable - even with detailed instructions and tools, agents still drifted on multi-step tasks 🐞 They’re impossible to debug - when they drifted, there was no clear root cause; we often resorted to trial-and-error to resolve issues.
We found ourselves giving our agents scripts to execute at each step of the workflow, and eventually came to the conclusion that scripting was just the better solution. We decided to put the agent at the coding step rather than the execution step, using LLMs to rapidly write scripts based on DOM context, and ultimately built BrowserBook as the tool we wished we had.
So what's included? The core IDE experience is purpose-built for web automation; some of its features include:
🌐 A fully-interactive inline browser instance that you can run Playwright automations against with the click of a button 📒 A Jupyter-notebook-style interface, so you can just run parts of your automation instead of the whole thing every time 🤖 A context-aware coding assistant so you don’t have to go digging for selectors 🤝 Helper functions for common actions like taking screenshots, data extraction, and managed auth profiles supporting username/password and TOTP for authenticated workflows
When you’re done building, you can run your automation manually through the IDE or via API for use in external agents or apps!
Our initial use case was healthcare automation, but if you’re building automated tests, writing browser-based RPA workflows, web scraping, or have an agent that needs to perform deterministic actions on the web, give us a try - we’d love to hear what you think!
Hey Product Hunt! 👋 I’m Chris, co-founder of BrowserBook here with teammates Jorrie and Evan.
We’re excited to share BrowserBook, an AI-powered IDE for building reliable, deterministic browser automations. It combines a notebook-style interface, an inline browser, and a context-aware coding assistant to help developers write, run, and iterate on Playwright scripts faster with built-in tools for screenshots, data extraction, and managed auth.
Why we built this
Jorrie and I started a healthcare automation company last summer, where we spent lots of time building back-office workflows (think insurance followup, medical coding, etc.) with custom browser agents. During this time, we ran into four major issues with browser agents:
💰 They’re expensive - we burned through tokens with all the workflow context we needed to provide
🐢 They’re slow - all that context let to super high latency on each request
😬 They’re unreliable - even with detailed instructions and tools, agents still drifted on multi-step tasks
🐞 They’re impossible to debug - when they drifted, there was no clear root cause; we often resorted to trial-and-error to resolve issues.
We found ourselves giving our agents scripts to execute at each step of the workflow, and eventually came to the conclusion that scripting was just the better solution. We decided to put the agent at the coding step rather than the execution step, using LLMs to rapidly write scripts based on DOM context, and ultimately built BrowserBook as the tool we wished we had.
So what's included?
The core IDE experience is purpose-built for web automation; some of its features include:
🌐 A fully-interactive inline browser instance that you can run Playwright automations against with the click of a button
📒 A Jupyter-notebook-style interface, so you can just run parts of your automation instead of the whole thing every time
🤖 A context-aware coding assistant so you don’t have to go digging for selectors
🤝 Helper functions for common actions like taking screenshots, data extraction, and managed auth profiles supporting username/password and TOTP for authenticated workflows
When you’re done building, you can run your automation manually through the IDE or via API for use in external agents or apps!
Our initial use case was healthcare automation, but if you’re building automated tests, writing browser-based RPA workflows, web scraping, or have an agent that needs to perform deterministic actions on the web, give us a try - we’d love to hear what you think!
How do I use it?
You can download for Mac at our website: https://browserbook.com
Cheers,
Chris