playwright-mcp-singleton-lock-workaround

Launch an isolated Chromium via ephemeral Playwright to resolve Chrome SingletonLock conflicts.

Updated Nov 18, 2025
One-click install
npx skills add https://github.com/cajias/claude-skills --skill playwright-mcp-singleton-lock-workaround
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-mcp-singleton-lock-workaround
Source: https://github.com/cajias/claude-skills/tree/main/plugins/integrations/skills/playwright-mcp-singleton-lock-workaround
Command: npx skills add https://github.com/cajias/claude-skills --skill playwright-mcp-singleton-lock-workaround

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps when Playwright MCP browser automation is blocked by a Chrome SingletonLock conflict because another session or teammate is already using the shared browser profile.

Core Features & Use Cases

  • Conflict diagnosis: Identifies the exact error pattern caused by Playwright MCP being pinned to a fixed user data directory.
  • Isolated fallback execution: Uses an ephemeral Playwright runtime to launch a separate Chromium instance without adding project dependencies.
  • Team-mode safety: Lets multiple agents work concurrently without killing another session's browser or disrupting teammate workflows.
  • Verification workflow: Provides a repeatable approach for checking UI state, capturing screenshots, and confirming browser actions in isolation.

Quick Start

Use this skill to run the browser check in an isolated Playwright session and capture evidence without conflicting with the existing MCP browser.

Frequently Asked Questions about playwright-mcp-singleton-lock-workaround

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does Playwright MCP browser automation fail with a Chrome SingletonLock conflict?

Playwright MCP fails with a Chrome SingletonLock conflict because another session or teammate is already using the shared browser profile directory. This lock contention blocks browser navigation, snapshot, and close actions across multi-agent team sessions.

How do I bypass Playwright SingletonLock conflicts without changing project dependencies?

You can bypass Playwright SingletonLock conflicts by launching an isolated Chromium instance through an ephemeral Playwright runtime. This fallback execution method verifies browser actions without adding or modifying any existing project dependencies.

Can I run multiple Playwright MCP agents concurrently in team mode without killing another session's browser?

Yes, you can run multiple Playwright MCP agents concurrently by using an isolated fallback execution approach. This team-mode safety mechanism launches separate ephemeral Chromium instances, preventing shared user-data-dir contention without disrupting teammate workflows.

What is the best way to capture browser screenshots when Playwright MCP is blocked by a stale process?

The best way to capture browser screenshots when blocked by a stale MCP process is to run an isolated Playwright session. This verification workflow captures UI state evidence in a separate Chromium instance without conflicting with the locked browser.

Does isolated Playwright execution support checking UI state when the shared browser profile is locked?

Yes, isolated Playwright execution supports checking UI state when the shared browser profile is locked. It provides a repeatable workflow for verifying browser actions, capturing screenshots, and confirming navigation in a separate ephemeral Chromium environment.