browser_visible

Configure browser launch modes by adjusting headed and private_mode parameters.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mrwyx12369/TeamPaw --skill browser-visible-mrwyx12369
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser_visible
Source: https://github.com/mrwyx12369/TeamPaw/tree/main/src/teampaw/agents/skills/browser_visible-en
Command: npx skills add https://github.com/mrwyx12369/TeamPaw --skill browser-visible-mrwyx12369

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use this skill to control the browser launch modes for browser_use, including visible vs headless operation and CDP/Playwright management.

Core Features & Use Cases

  • Supports two launch modes: managed CDP and Playwright private_mode
  • Allows toggling headed for visible vs headless operation
  • Use case: automate tests that require a visible browser or a headless session

Quick Start

Start the browser with default CDP control and adjust headed and private_mode as needed.

Frequently Asked Questions about browser_visible

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

FAQPage Schema
How do I launch a visible browser for Playwright automation debugging?

To launch a visible browser in Playwright automation, toggle the headed parameter to enable headful mode. This allows you to visually monitor browser actions during testing or debugging while maintaining CDP control over the session.

What is the difference between headed and private_mode in browser automation?

Headed controls visible versus headless browser operation, while private_mode toggles between managed CDP and Playwright-managed sessions. Headed affects browser visibility, whereas private_mode determines the underlying automation control mechanism.

Can I use CDP to control a headless Playwright browser session?

Yes, you can use CDP to control a headless Playwright browser session by setting headed to false and private_mode to false. This configuration uses managed CDP for background automation tasks without a visible browser window.

When should I use private_mode versus CDP-managed browser launch?

Use private_mode for Playwright-managed isolated sessions suited to testing, or use CDP-managed launch for direct browser debugging and automation control. Private_mode provides Playwright session isolation, while CDP offers direct connection management.

Does this browser launch mode skill support headless automation workflows?

Yes, the skill supports headless automation workflows by setting the headed parameter to false. This configures the browser to run without a visible interface, suitable for background automated tasks and continuous integration testing.