Why contexts[0] and not a new context?

contexts[0] is the profile. It holds the profile's cookies, storage and logins. A context you create yourself is a throwaway one outside the profile.

What does our PC need?

Windows and a real graphics card. A start on a software renderer is refused, and macOS and Linux are coming soon. Bring your own proxy for real work and count 250 to 400 MB per running browser; your plan and your PC decide how many run at once.

Do our logins come over from Browserbase?

No, each new profile starts signed out. Sign in once per site and the profile stays signed in, or let your agent store the login in the profile's vault without seeing the password.

Should our agent use CDP or MCP?

Either, per agent. Over CDP your code keeps full control of the browser. Over MCP every click takes a human pointer path, logins come from the vault unseen, and the agent reads a compact page map: 462 tokens per step, measured on Hacker News.

Can we try it before we cancel Browserbase?

Yes, free and without a card. The Free plan runs 1 browser at once with 3 profiles. Start, Solo and Studio are each free for 7 days, so you can run your agent on the plan you would pick.

Switching from Browserbase

Move your agent's browsers from the cloud to your PC.

Playwright connects to a profile on your own PC instead of a cloud session, so only the lines that start the browser change. Each profile keeps its own identity, cookies and logins between runs.

Download free for Windows Read the CDP docs

Free plan with 3 profiles · No credit card · Runs on your PC

One email with the download link, nothing else. Privacy

Read the CDP docs

Free plan with 3 profiles · No credit card · Runs on your PC

With Browserbasecloud session

With Scalebrowseryour PCAgent code unchanged

payouts.py

1bb = Browserbase(
2    api_key=os.environ["BROWSERBASE_API_KEY"])
3 
4session = bb.sessions.create()
5browser = playwright.chromium.connect_over_cdp(
6    session.connect_url)
7 
8page = browser.contexts[0].pages[0]
9 
10page.goto("https://dashboard.stripe.com/payouts")
11rows = page.locator("tbody tr").all_inner_texts()
12for row in rows:
13    print(row)
14browser.close()

$python payouts.py

→ sessions.create()Browserbase

← session.connect_url

payouts.py

1sb = ScalebrowserClient(
2    base_url="http://127.0.0.1:8787",
3    token=os.environ["SCALEBROWSER_TOKEN"])
4started = sb.start_profile(PROFILE_ID)
5browser = playwright.chromium.connect_over_cdp(
6    started.cdp_ws, no_defaults=True)
7context = browser.contexts[0]
8page = context.pages[0] if context.pages else context.new_page()
9 
10page.goto("https://dashboard.stripe.com/payouts")
11rows = page.locator("tbody tr").all_inner_texts()
12for row in rows:
13    print(row)
14browser.close()

$python payouts.py

→ 127.0.0.1:8787Scalebrowser

← started.cdp_ws

Payouts · Nordlicht Home

dashboard.stripe.com/payouts🇩🇪Shop EU 01

Payouts

€932.10In transit•••• 4021Nov 9

€1,284.50Paid•••• 4021Nov 7

€2,045.80Paid•••• 4021Nov 4

What stays, what starts fresh, what you gain.

Your agent's code keeps working as it is. Where its browsers run, their proxies and their logins are set up new in four steps.

Stays the same

Your agent's code
Every call after the start runs as before: the same pages, clicks and reads, in the same Playwright calls.
Playwright, Puppeteer, Selenium
A profile's start hands back cdp_ws for connect_over_cdp and puppeteer.connect, and debug_port for chromedriver.
Headless runs
Your runs can stay in the background. Each start picks headless or a window you can watch and work in.

Starts fresh

Where the browsers run
On your Windows PC with a real graphics card, instead of a cloud. macOS and Linux are coming soon.
1Install Scalebrowser on your PC
The session lines
There is no Browserbase-compatible API. The lines that create a session become a start of the profile.
2Connect your agent
Your proxies
You bring your own. Scalebrowser checks each one and sets the profile's time zone and language to its country.
3Create profiles from a preset
Your logins
They start fresh in each new profile: sign in once per site, or let your agent store the login in the vault without seeing it.
4Sign in once per site

What you gain

An identity from your PC
Each profile runs on your own PC: graphics card and screen come from its real hardware, time zone and language from its proxy.
Logins the agent never sees
Each profile keeps its cookies and logins, and your agent signs in from its vault without ever seeing the password.
Workflows
Turn a repeat job into a workflow of 89 blocks, run it over many profiles and start it on a schedule, by webhook or from your agent.
Run videos
A run becomes a video with zoom on the clicks and a cursor that follows, shared by link.
Pay by browsers at once
Plans count the browsers running at the same time: Solo runs 5 at once with 100 profiles for $49 a month.

The move, in four steps.

From the install to the last login, with your agent's code as it is.

Step 1: Install Scalebrowser on your PC
The Windows app runs the profiles and serves the REST API, MCP and CDP on 127.0.0.1:8787, behind a token.
Step 2: Connect your agent
Hand a profile's cdp_ws to Playwright's connect_over_cdp, or add Scalebrowser to Claude Code, Cursor or ChatGPT over MCP.
Step 3: Create profiles from a preset
Your proxies are checked first. Then each new profile gets its own identity in its proxy's country.
Step 4: Sign in once per site
Each new profile starts signed out. Sign in once and it stays signed in, or let your agent store the login in the profile's vault without seeing the password.

Before you switch, short answers.

A line or two each. Every call and field is in the CDP docs.

No, the start lines change.

Start a profile with ScalebrowserClient and hand started.cdp_ws to Playwright's connect_over_cdp. Everything your agent does after that line stays as it is. See the CDP docs.

Your agent stays as it is. Its browsers move to your PC.

Install Scalebrowser, start a profile, and connect Playwright to it or your agent over MCP.

Download free for Windows