skills.rest
mukles
muklesCOMMUNITY
Explore all skills by this author →
Website𝕏@mukles_devGitHub

browser-debug-setup

Establish a persistent Chrome debugging session on port 9222.

Updated Sep 16, 2025
Search Tags:#automation#debugging#chrome#browser#profiles#remote-debugging
One-click install
npx skills add https://github.com/mukles/platejs-markdown-converter --skill browser-debug-setup-mukles
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser-debug-setup
Source: https://github.com/mukles/platejs-markdown-converter/tree/main/.agents/skills/browser-debug-setup
Command: npx skills add https://github.com/mukles/platejs-markdown-converter --skill browser-debug-setup-mukles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill establishes and maintains a single persistent Chrome debugging session to avoid repeated setup for agent browser tasks.

Core Features & Use Cases

  • Create and reuse a dedicated Chrome profile with remote debugging enabled at 127.0.0.1:9222.
  • Clone and preserve a signed-in profile to minimize login prompts while keeping isolation from the user's daily profile.
  • Verify the debugging endpoint is alive (json/version) and connect to a persistent page like persistent-main.
  • Cross-platform launch guidance: macOS users can start a separate Chrome instance with a dedicated user-data-dir and remote debugging port.
  • Use case: long-running automation sessions requiring stable debugging context across tasks.

Quick Start

Launch the dedicated debug browser with a separate user-data-dir, sign in once, and connect your automation to http://127.0.0.1:9222.

Frequently Asked Questions about browser-debug-setup

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

FAQPage Schema
How do I keep a Chrome remote debugging session persistent across automation tasks?▼

To maintain persistent Chrome remote debugging, launch a dedicated browser instance with a separate user-data-dir and remote debugging port 9222, preserving page state and avoiding repeated setup for long-running automation tasks.

Why does my browser automation lose its login state and require re-authentication?▼

Browser automation loses login state when using a temporary profile. Cloning a signed-in Chrome profile to a dedicated user-data-dir isolates your daily profile while minimizing login prompts across automation sessions.

Can I run a separate Chrome instance for debugging on macOS without affecting my main profile?▼

Yes, on macOS you can start a separate Chrome instance using a dedicated user-data-dir and remote debugging port 9222, keeping the debug browser isolated from your daily profile while enabling stable automation context.

How do I verify that a Chrome remote debugging endpoint is alive and ready for connections?▼

Verify the Chrome remote debugging endpoint by checking the json/version response on 127.0.0.1:9222. Once alive, connect your automation to a persistent page like persistent-main for stable task execution.

What's the best way to avoid repeated browser setup for agent web automation?▼

The best way to avoid repeated browser setup is establishing a single persistent Chrome debugging session. By reusing a dedicated profile with remote debugging on port 9222, agents maintain stable page state across tasks.

Related Skills

Explore More Software Engineering Skills→
udecodeudecode
434

browser-debug-setup

Set up a persistent Chrome debugging environment with a dedicated profile.

Official
Intermediate
githubgithub
37.6k

chrome-devtools

Automate browser control and debugging via the Chrome DevTools MCP.

Official
Advanced
LuminairPrimeLuminairPrime

mcp-chrome-devtools

Debug and automate web pages through the Chrome DevTools interface.

Community
Advanced
tysonthomas9tysonthomas9
3

vercel-sandbox

Run agent-browser with headless Chrome inside ephemeral Vercel Sandbox microVMs.

Community
Advanced