Browser is already in use for <profile-dir>, use --isolated to run multiple instances of the same browser

What it means

Playwright MCP keeps its browser state in a profile folder, and one folder serves one browser at a time. A second client that starts with the same settings points at the same folder, and its launch stops with this message.

The message is sometimes the wrong diagnosis. When Chrome crashes on launch, for example from a missing system library, Playwright MCP reports "already in use" with nothing running (issue 1305). If you see it on the first call with nothing else open, suspect a crash.

Fix it

1. Close the other client or browser that uses the same profile. An agent session that did not exit cleanly counts.
2. Or add --isolated to the server's args. Each instance then gets its own profile, so several can run side by side:

   {
     "mcpServers": {
       "playwright": {
         "command": "npx",
         "args": ["@playwright/mcp@latest", "--isolated"]
       }
     }
   }

3. On a first call with nothing else open, run Chrome by hand from the Playwright cache to read the real error. On Linux, npx playwright install-deps installs missing system libraries, and a container running as root needs --no-sandbox.

With superbot

This is a local setup error, and superbot does not fix it. superbot is an alternative if the goal is a page opened in a browser.

superbot opens a page in a browser session through its one tool, and you can click, type and fill forms in it. The session runs in the browser on your own computer when your account has one linked, else in a cloud browser.

It does not use a Playwright MCP profile folder, so this error does not apply to it.

A real run is on the Executable doesn't exist page. Its reply says the session ran in a cloud browser.

This needs an account.
An agent with none signs you in through /auth.md.
You read back one emailed code.

Related

• browserType.launch: Executable doesn't exist at <path>
• spawn npx ENOENT
• ✘ Failed to connect