Hey PH - today we re rolling out configurable proxies for API-based execution in BrowserBook.
One of the most common reasons browser automations fail in production is bot detection. Captchas, IP reputation issues, geo restrictions, and rate limits can derail even solid Playwright workflows once you start running them at scale.
Congrats on shipping BrowserBook!
The “agent at the coding step, not the execution step” idea really resonates — I’ve hit the same issues with browser agents being slow, expensive and impossible to debug.
The inline browser + notebook flow looks perfect for iterating on automations.
Excited to try this for some internal RPA-style workflows 🙌
BrowserBook
@patch_app Thank you! Let us know how it goes and if we can help in any way.
Cool! Lately I’ve been seeing a lot of new browser apps, a great niche.