skills.rest
matevip
matevipCOMMUNITY
Explore all skills by this author →
GitHub

browser_visible

Control visible browser windows for demonstrations and manual debugging via headed mode and CDP port options.

839|277|Updated Apr 4, 2026
Search Tags:#debugging#demo#browser-automation#headed-mode#visible-browser#cdp-port
One-click install
npx skills add https://github.com/matevip/mateclaw --skill browser-visible-matevip
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser_visible
Source: https://github.com/matevip/mateclaw/tree/main/mateclaw-server/src/main/resources/skills/browser_visible
Command: npx skills add https://github.com/matevip/mateclaw --skill browser-visible-matevip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables launching a real browser window in visible mode for demonstrations, debugging, or scenarios where human participation is required.

Core Features & Use Cases

  • Start a visible browser window with controllable headed mode and CDP port for debugging and demonstration purposes
  • Expose manual interaction points during demos or QA sessions while keeping automation control
  • Manage startup parameters such as headed and cdpPort to tailor the browser session for different environments

Quick Start

Start a visible browser session with browser_use(action="start", headed=true) and then open the target page with browser_use(action="open", url="https://example.com").

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 debugging and demonstrations?▼

To launch a visible browser for debugging, use the browser_use tool with the action parameter set to start and headed set to true, which opens a real browser window for manual interaction and automation control.

Can I expose manual interaction points during QA sessions while keeping automation control?▼

Yes, you can expose manual interaction points during QA sessions by starting a visible browser session with headed mode enabled, allowing human participation while maintaining automated browser control.

How does the CDP port work for browser debugging sessions?▼

The CDP port specifies a debugging port for browser sessions, enabling remote debugging and inspection of the visible browser window during demonstrations or collaborative work where human interaction is required.

What is the best way to start a browser automation session for collaborative work?▼

The best way to start a browser automation session for collaborative work is to use browser_use with headed mode and a configured CDP port, allowing participants to view and interact with the browser while automation runs.

Do I need any specific dependencies to run a visible browser session?▼

No specific dependencies are required to run a visible browser session, as the skill relies on the browser_use tool to start and manage sessions with headed and cdpPort parameters for visibility and debugging.

Why does my browser automation run in headless mode instead of showing a visible window?▼

Browser automation runs in headless mode when the headed parameter is not set to true, so you must explicitly pass headed=true in browser_use to force a visible browser window for demos and debugging.

Related Skills

Explore More Software Engineering Skills→
citedycitedy
31

browser_visible

Launch headed browser sessions with browser_use for visible GUI interactions.

Official
Intermediate
Research-EqualityResearch-Equality
9

browser_visible

Launch a headed Chromium browser for interactive research tasks with a visible UI.

Official
Intermediate
AskTinNguyenAskTinNguyen

browser-testing-with-devtools

Inspect live pages, DOM, console logs, and network activity via Chrome DevTools MCP.

Community
Advanced
burgebjburgebj

browse

Automate web interactions and capture screenshots in a headless browser.

Community
Advanced