Browserbase Changelog

Web automation for everyone!

Director makes it so you don’t have to start writing code to use Browserbase. You can start with the task that you already know—the boring work that you want to automate. And then, using AI by chatting with the application, it outputs a Stagehand script that controls the browser.

Where’s that browser running? Browserbase—the best infrastructure platform for running browsers at scale in the cloud.

Try it now at Director.ai

We’re excited to finally announce Stagehand for Python.

To get started:

1. Run pip install stagehand
2. Review the Github: https://github.com/browserbase/stagehand-python
3. Automate the web

Have fun!

The Browserbase playground is used to develop and test scripts before putting them into production. Previously, our playground only supported Playwright, but we’ve now added our open source browser automation framework, Stagehand.

You’ll see new script templates, a “convert to Stagehand” button, and you can add in new commands in the console after running.

Our new Hobby plan is only $20 a month, renamed → “Developer Plan”. For current Hobby customers, this will be reflected in your next invoice.

We’ve also increased concurrency across every plan!

See all the changes on https://browserbase.com/pricing

Leveraging the Stagehand API, Browserbase can now offer a deeper look into Stagehand script executions. This enhanced observability will help users better understand and optimize their Stagehand usage and also provide debugging insights that significantly reduce troubleshooting time and improve the overall developer experience.

Key features include method inspection views, element highlighting for actions, and detailed execution metrics.

Browserbase has moved all remaining customers from single user accounts to multi-user and multi-project supported Organizations.

This means your team can have their own logins, see sessions across shared projects, and manage multiple projects under one org. Or if you’re building alone, you can have multiple projects within your account.

No action required on your part. Read more here.

We now ship the captchaImageSelector and captchaInputSelector browser settings in the API docs and in the SDKs!

const sesssion = await bb.sessions.create(body: {
  projectID: BROWSERBASE\_PROJECT\_ID,
  browserSettings: {
    captchaImageSelector: "",
    captchaInputSelector: "",
    }
});

We also now have two new versions of our SDKs with a lot of internal improvements!

• Node: v2.6.0: https://www.npmjs.com/package/@browserbasehq/sdk/v/2.6.0
• Python: v1.4.0: https://pypi.org/project/browserbase/1.4.0/

Read more: https://docs.browserbase.com/features/stealth-mode#custom-captcha-solving

Keep-alive is more reliable now!

When a session is created with keepAlive: true, a protection is set on the browser. This prevents it from being stopped on disconnect. The session is only stopped if:

• The user stops the session via the API or dashboard
• The session expires
• Connect stops the session due to an error

Previously, the keepAlive protection expired based on a coarse timer. It now uses more precise timing, making protection behavior more accurate and reliable.

Read more: https://docs.browserbase.com/guides/long-running-sessions#keep-alive-sessions

Session cookies are now fully persisted resulting in fewer session timeouts!

What changed?

Basic & Advanced Stealth were both updated such that contexts will now persist session cookies (cookies with expires: -1). The cache that is saved from session to session has been slimmed down, decreasing the rate at which contexts grow in size with persist: true.

What results should customers see?

Primarily, this increases the lifespan of the context 🎉 Sessions created with contexts are significantly less likely to time out when you try to connect.

This also means login flows are persisted across sessions more reliably.

Resources:

• Learn more: https://docs.browserbase.com/features/contexts
• Code Examples: Contexts code example & using Stagehand to login to Github

Browserbase now supports UI-based workflows involving native select elements! Previously, clicking on a select HTML element in the live view wouldn’t show the native options popup, which meant that the only way users could edit these elements was via keyboard. This is now fixed! Users in the live view will now see a menu as expected. Click away :)

We’re thrilled to announce the release of Stagehand 2.0, bringing significant improvements to make browser automation more powerful, faster, and easier to use than ever before.

🚀 New Features

• Introducing stagehand.agent: A powerful new way to integrate SOTA Computer use models or Browserbase’s Open Operator into Stagehand with one line of code! Perfect for multi-step workflows and complex interactions. Learn more
• Lightning-fast act and extract: Major performance improvements to make your automations run significantly faster.
• Enhanced Logging: Better visibility into what’s happening during automation with improved logging and debugging capabilities.
• Comprehensive Documentation: A completely revamped documentation site with better examples, guides, and best practices.
• Improved Error Handling: More descriptive errors and better error recovery to help you debug issues faster.

🛠️ Developer Experience

• Better TypeScript Support: Enhanced type definitions and better IDE integration
• Better Error Messages: Clearer, more actionable error messages to help you debug faster
• Improved Caching: More reliable action caching for better performance

We’re excited to see what you build with Stagehand 2.0! For questions or support, join our Slack community.

For more details, check out our documentation.

Now updated for Chrome version 132 - Better defaults (like laptop sizing), new features (like realistic screen dimension sizes), and increased stealth (new device data).

Talk to our team for access, and trial, or more info!