Parallel AI agents on Windows
Run several AI agents at once, each in its own browser profile.
Connect Claude Code, Cursor and other MCP apps to MetaDock at the same time. Each agent gets its own browser profile with its own logins, and you watch them all side by side. Free with 3 profiles and 6 open browsers.
An AI agent asks for several browsers; MetaDock opens isolated browsers in a grid and the agent works in all of them in parallel
One app, many agents
How do I run several Claude Code sessions that each need a browser?
Every session connects to the same running MetaDock and opens its browser in the profile you name, so no session is locked out by another's profile and none of them starts logged out.
One profile per agent
Every profile keeps its own cookies, storage, cache, extensions and logins. Two agents never share a session unless you point them at the same profile.
Signed in from the first step
Log in once by hand in each profile. MetaDock keeps the session on disk across restarts, so every agent starts signed in instead of at a login page.
All of them side by side
Every browser your agents open is tiled in one layout, so the one that is stuck stands out. On MetaDock Pro, spread layouts across several monitors.
Every MCP app, one server
Claude Code, Claude Desktop, Cursor, VS Code, Codex and most other MCP clients that run on your PC. 154 tools; the MCP server is on every plan.
Why MetaDock
How is this different from one browser MCP server per agent?
Two agents, one browser profile, and nothing works.
The problem
A second Claude Code session clashes with the first, because a browser profile can only be used by one browser at a time.
A fresh, empty profile per agent avoids the clash, but every agent and subagent starts logged out and stops at a login page.
Sharing one browser between agents means every agent acts as the same account.
Agents run in windows scattered across your screen, or headless where you cannot see them at all.
| Feature | MetaDock | Playwright MCP or Chrome DevTools MCP |
|---|---|---|
| Several agents at once | Every agent connects to the one running app and opens browsers in its own profile | The default profile serves one browser at a time; more agents need --isolated or their own profile directory |
| Logins | Each profile keeps its logins on disk, so an agent starts signed in | A persistent profile keeps logins and --isolated starts logged out; both can also attach to a browser you already have open |
| A different account per agent | One profile per agent, each with its own cookies, storage, cache and extensions | One profile directory per agent, managed by hand |
| Browsers | Microsoft Edge WebView2 on Windows 10/11 | Chrome, Edge, Firefox and WebKit (Playwright MCP) or Chrome (Chrome DevTools MCP), on Windows, macOS and Linux |
| Price | Free within the limits; MetaDock Pro $49/mo flat | Free and open source (Apache-2.0) |
Playwright MCP and Chrome DevTools MCP behaviour from their READMEs and Chrome DevTools MCP's Advanced usage guide, as of October 25, 2026. Both are free tools that suit many jobs well. Verify current details on each project's site before deciding.
Steam reviews
What people are saying
“Brilliant software. Main use case for me is the ability to resize windows that can't usually be resized. I'm able to do almost as much on 2 monitors now as I could on 3.”
“Very interesting application, great for productivity. This has fast become a tool in my tool box.”
All quotes are from pseudonymous Steam reviewers. Verify on Steam. Reviews curated and re-checked against the live page as of 2026-10-17.
FAQ
Running agents in parallel
Yes. Each session connects to the MetaDock app that is already running and opens its own browsers. Each time MetaDock starts, it asks you before a new AI app can connect.
Create one profile per account and log in to it once by hand. Then ask each agent to open its browser in that profile by name. Each profile has its own cookies, storage, cache and extensions, so the agents do not share a session. Use separate accounts and automation only where each site's terms allow them.
As many as you like. On the free MetaDock they share 3 profiles and 6 open browsers. MetaDock Pro has no licensed limit, so it comes down to your machine's memory and CPU.
Yes, on MetaDock Pro: headless mode runs a browser with no window. Visible browsers are the default, because watching the agents is the point for most people.
You are. MetaDock gives the agent a browser and shows you what it does, but it does not check or block the agent's decisions, and an agent can act faster than you can step in. Use agents only in accounts and on sites whose terms allow automation, and see the EULA for the full terms.
Trial and guarantees
14-day free trial, no signup
Download it and start a 14-day free trial in the app. No account, no email, no card. Then keep Pro or carry on free.
Cancel anytime
Pro renews automatically until you cancel, and you can cancel from the billing portal at any time to stop every future charge.
Local-first data
Multi-monitor layouts, profiles, and browsing data stored locally. No cloud sync.
Every agent, its own browser, all on one screen.
Free, with 14 days of MetaDock Pro to start. No account, no email, no card. Windows 10/11.
- 14-day free trial
- No account or email
- No credit card
You may also be interested in...
Other jobs MetaDock does for you and your AI agents
A logged-in browser for your agent
Log in once by hand. The agent works inside the session without your password.
Watch the agent and take over
By default every browser it drives is visible. Click in whenever you choose.
Compare browser MCP servers
MetaDock next to Playwright MCP, Chrome DevTools MCP, Browser Use and cloud browsers.
Playwright, Chrome, Chrome DevTools, Claude Code, Claude Desktop, Cursor, VS Code, Codex, Microsoft Edge, WebView2, Firefox, WebKit, Windows, macOS and Linux are trademarks of their respective owners. MetaDock is not affiliated with, sponsored by, or endorsed by any of them. Comparisons reflect publicly available information on the date given and may change.