Repository navigation
what a second browser costs
The session can hold two browsers, main and support, and the reason to know
what the second one costs is that the answer is not "a bit more". Measured on
2026-09-17 on one Windows machine, reading the whole process tree rather than the
parent:
| state | resident memory | processes |
|---|---|---|
| the MCP server, no browser | 77 MB | 2 |
| one browser open | 704 MB | 10 |
| two browsers open | 1,261 MB | 18 |
| the second browser alone | 556 MB | 8 more |
The second browser is 79% on top of the first, not a rounding error. Eight more processes, because Firefox is multiprocess and a second browser brings its own set.
A single browser at 704 MB fits on a 2 GB machine with room to work. Two at 1,261 MB is most of a 2 GB machine before the pages have anything heavy on them, and the figures above are with blank pages: real content pushes content processes up from here.
So the practical line: two browsers wants 4 GB, and on 2 GB you should open the second one deliberately and close it when the comparison is done. The wider disk-and-memory picture for running any of this yourself is in what a self-hosted AI agent costs to run.
The server itself, at 77 MB and two processes, is nothing. All of the cost is the browsers, which is the same conclusion the self-hosting measurement reached from the other direction.
It earns 556 MB when the task genuinely needs two views at the same moment:
- a reference open while a form is being filled, so checking something does not navigate away from half-entered state;
- two accounts side by side;
- the same page from two exits, which is the only honest way to compare markets at one moment rather than two minutes apart, as in seeing a page as it appears in another country;
- a clean second opinion on a page that is behaving oddly in a browser that has been clicking around for twenty steps.
It does not earn it for doing two unrelated jobs. Two sessions is cleaner there: separate processes, separate failures, and one browser's memory freed when its job ends.
browser_close with the browser named. Worth saying because the natural habit
is to leave both open for the rest of the conversation, and the second one goes
on holding half a gigabyte while nothing is using it.
The identities and the focus rule, which are the other half of running two, are in two browsers in one session.
The method is the part to copy, because the absolute numbers are one machine and one set of blank pages:
- Find the server process and read its resident memory including children. Reading the parent alone reports about a tenth of the truth here, since the parent is the Python process and the browsers are its descendants.
- Take a reading with no browser, one browser, and two.
- Subtract.
That is three readings and a subtraction, and it tells you what your pages actually cost rather than what a blank one does.
How much memory does a browser agent use? Measured here: 704 MB for the server plus one browser across ten processes, on a blank local page. Real pages are higher.
How much does a second browser add? 556 MB and eight processes, a 79% increase on the first.
Can I run two browsers on a 2 GB machine? One comfortably, two barely and not with heavy pages. Plan on 4 GB if two are normal for your work.
Why is the parent process only using a few dozen megabytes? Because it is the Python side. The browsers are separate processes and you have to sum the tree to see them.
Should I use two browsers or two sessions? Two sessions for unrelated jobs, which also frees the memory when one finishes. Two browsers when one task needs both views at once.
See also: two browsers in one session for the behaviour, including the focus rule that catches people, and what a self-hosted AI agent costs to run for the disk and startup side of the same question.
- Measured 2026-09-17 on one Windows 11 machine, reading resident memory across the MCP server process and all of its descendants at three points: before opening a browser (77 MB, 2 processes), after
browser_open(704 MB, 10 processes), and afterbrowser_openwithbrowser: support(1,261 MB, 18 processes). Both browsers were headless and on blank pages.
Three readings and a subtraction. The reason the number is worth having is that "a second browser" sounds cheap and is 79%.
- OpenAI Operator alternatives
- Open-source Operator-style agents
- Is OpenAI Operator still available?
- OpenAI Operator vs Claude computer use
- browser-use alternatives
- Choosing an AI browser agent
- Open-source AI browser agents
- Open-source computer-use agents
- What is an AI web agent?
- AI browser agents vs traditional scraping
- Cloud browser infrastructure for AI agents, explained
- Browserbase alternatives
- Firecrawl vs an AI browser agent
- Skyvern alternatives
- Stagehand vs browser-use
- Project Mariner is gone: what replaced it
- Manus alternatives
- Gemini computer use vs Claude computer use
- A stealth browser MCP, reviewed honestly by its own wiki
- AI browser vs AI browser agent: which one do you want?
- AI browser agent vs RPA: which one fits the job
- AI browser agent vs n8n, Zapier and Make
- Vercel agent-browser alternatives, compared honestly
- What is an agentic browser? Definition and the two kinds
- Open-source agentic browsers: the three layers, compared
- Choosing an MCP server for browser automation: four axes
- Stealth MCP servers compared: Camoufox, nodriver, Patchright
- Playwright MCP alternatives, and the three you don't need
- Autonomous browser agents: the four rungs of autonomy
- What is actually free in the AI browser agent stack
- browser-use on GitHub: what the repo actually gives you
- Playwright MCP vs Chrome DevTools MCP: different jobs
- How to choose among MCP servers: a map by category
- Which MCP servers are worth adding to Claude Code
- MCP on GitHub: finding servers and judging them fast
- MCP vs an API: the decision, and what the wrapper costs
- MCP alternatives: when the protocol is the wrong shape
- Why does my AI agent get blocked?
- The timing signal AI agents give off
- Agent retry loops trip rate limits, not fingerprints
- Claude computer use detected as a bot
- browser-use getting blocked: what you can and cannot change
- Playwright MCP session blocked: four causes, four fixes
- Playwright MCP and captchas: what actually gets you past
- Cloudflare and a browser MCP server: what is being read
- Can an AI agent solve a captcha? The honest answer
- Getting an AI agent to fill out forms
- The best model for an MCP browser agent, and what it really costs
- Browser problem or model problem?
- How to use a Playwright MCP server with Claude Code
- Extracting data to a CSV with an AI agent
- Monitoring a page for changes with an AI agent
- How to let Claude Desktop control a browser
- How to add a browser to Cursor as an MCP server
- Using an AI agent to hunt for apartments
- Getting website data into Google Sheets with an AI agent
- Using an AI agent to download invoices from portals
- AI agents for web research
- Using an AI agent to test your own website
- How to add a browser to Cline as an MCP server
- Posting to social media with an AI agent
- Posting to Facebook with an AI agent
- Posting to Instagram with an AI agent
- Posting to X with an AI agent
- Automating LinkedIn posts: read this first
- Appointment bots: what they are and what an agent can legitimately do
- Track prices across sites with an AI agent
- Build a lead list with an AI browser agent
- Run an AI browser agent on a schedule
- AI browser agent with a local LLM: what changes
- Should you log your AI agent into your accounts?
- How to write a task an AI browser agent can follow
- Move data between two web apps with an AI agent
- The MCP server
- How the tools are shaped, and why
- Playwright MCP vs the Playwright CLI: which fits when
- Playwright MCP: browser is already in use, and the fix
- Playwright MCP best practices: four decisions that matter
- Playwright MCP with a proxy, and the three leaks it leaves
- A browser MCP server in GitHub Copilot: setup and limits
- Using a browser MCP server for web scraping: the pattern
- Which LLM for browser automation: the four properties
- How to build a browser agent, and what to take instead
- Getting an AI agent to log into a website: three routes
- MCP tools, resources and prompts: who controls each
- How many MCP tools is too many? The context arithmetic
- How to build an MCP server: the decisions, not the scaffold
- Local or remote MCP server: what changes, and what does not
- Writing an MCP client in Python: the thirty-line version
- Self-hosted AI agent: what one actually costs to run
- How long an AI browser agent takes per step, measured
- Text, HTML, snapshot or screenshot: what the agent should read
- Giving an AI browser agent a stopping condition
- Keeping an AI browser agent out of destructive actions
- Why did the AI agent click the wrong thing
- When the page changes under the AI agent
- Running one AI agent task across a list of sites
- Seeing a page as it appears in another country
- Getting data out of a dashboard with no export button
- Two browsers in one session: main and support
- Finding the dead links on a site with an AI agent
- Filling a CRM record from a company's website
- One form submission per spreadsheet row, with an AI agent
- Dated screenshots of a page as evidence
- Checking order and delivery status with an AI agent
- Reading a PDF that opens inside the browser
- Summarising a long page or thread with an AI agent
- Collecting every image on a page with its caption
- Collecting event and course listings with an AI agent
- Cancelling a subscription with an AI agent
- What an AI agent can and cannot do inside an iframe
- Shadow DOM and an AI agent: you can click it, you cannot read it
- How to add a browser to Codex as an MCP server
- What a page snapshot costs, per control
- How to let Gemini CLI use a browser
- Native selects and the ones that only look like selects
- Clicking by selector or by coordinates
- How long the agent waits before it gives up
- What a second browser costs
- Uploading a file with an AI agent, and why this one cannot
- Watching the agent work, and when it is worth it
- When not to use an AI browser agent
- Agent or script: deciding once instead of every time
- Using the keyboard instead of the mouse
- Secrets in an agent task: where they end up
- What an agent run should log
- Deduplicating what an AI agent collects
- Normalising values across sites
- Validating an AI agent's output
- Reading a table with an AI agent
- Driving a site's own search and filters
- The task works headed and fails headless
- How to let the AdaL CLI use a browser