Which settings change on the attached profile?

Four, all about the browser. Set highlight_elements=False so browser-use adds no marker of its own to the page. Leave out user_data_dir and storage_state, put the proxy on the profile, and stop the profile through Scalebrowser: stopping the agent leaves the browser running.

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?

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.

Can our coding agent drive the profile instead?

Yes, over MCP. Leave out your own agent loop and let Claude Code, Codex, Cursor or another MCP client drive the profile. It reads a compact page map: 462 tokens per step, measured on Hacker News.

Can we try it before we move our agents?

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 browser-use

Keep browser-use. Give it a profile on your own PC.

Hand browser-use a profile's CDP address and one line changes; the task, the model and the agent loop stay. Or let your coding agent drive the profile over MCP.

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 browser-usethe browser you use today

With Scalebrowseryour PCAgent code unchanged

agent.py

1import asyncio
2 
3from browser_use import Agent, Browser, ChatOpenAI
4 
5 
6 
7async def main():
8 
9 
10 
11 
12    browser = Browser(…)
13 
14    agent = Agent(
15        task="Reply to this week's new reviews on Etsy",
16        llm=ChatOpenAI(model="gpt-5.5"),
17        browser=browser,
18    )
19    await agent.run()
20 
21 
22asyncio.run(main())

$python agent.py

→ Browser(…)browser-use

← agent.run()

agent.py

1import asyncio
2import os
3from browser_use import Agent, Browser, ChatOpenAI
4from scalebrowser import AsyncScalebrowserClient
5PROFILE_ID = "prf_7d2a…"   # an existing profile
6 
7async def main():
8    sb = AsyncScalebrowserClient(
9        base_url="http://127.0.0.1:8787",
10        token=os.environ["SCALEBROWSER_TOKEN"])
11    started = await sb.start_profile(PROFILE_ID)
12    browser = Browser(
13        cdp_url=started.cdp_ws, highlight_elements=False)
14    agent = Agent(
15        task="Reply to this week's new reviews on Etsy",
16        llm=ChatOpenAI(model="gpt-5.5"),
17        browser=browser,
18    )
19    await agent.run()
20    await sb.stop_profile(PROFILE_ID)
21 
22asyncio.run(main())

$python agent.py

→ 127.0.0.1:8787Scalebrowser

← started.cdp_ws

Reviews · NordlichtHome

etsy.com/your/shops/me/reviews🇩🇪Shop EU 01

Reviews3 new this week

Lena F.Beautiful lamp, arrived fast.New

Jonas W.Lovely, the cable is a little short.New

Mila H.Exactly as pictured. Thank you!New

What stays, what starts fresh, what you gain.

Your agent keeps working as it is. The browser it uses, its proxy and its logins are set up new in four steps.

Stays the same

Your agent's code
The task, the model and the agent loop stay; only the line that makes the browser takes the profile's address.
browser-use over CDP
browser-use talks to its browser over CDP, and every profile hands out a CDP address on your PC.
Your model and your key
The agent keeps calling the model you chose with your own key. Scalebrowser only supplies the browser.

Starts fresh

Where the browser runs
On your Windows PC with a real graphics card. macOS and Linux are coming soon.
1Install Scalebrowser on your PC
The browser line
Browser() takes the profile's CDP address. Leave out user_data_dir and storage_state: the profile keeps its cookies, storage and logins.
2Connect your agent
Your proxies
You bring your own and set it on the profile, not in browser-use. Scalebrowser checks it and sets 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 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
Pass started.cdp_ws to Browser(cdp_url=…), or let Claude Code, Codex or Cursor drive the profile 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.

Yes, one line changes.

Hand the profile's address to Browser(cdp_url=started.cdp_ws, highlight_elements=False). The task, the model and the agent loop stay as they are. See the CDP docs.