skills.rest
udecode
udecodeOFFICIAL
Explore all skills by this author →
WebsiteGitHub

browser-debug-setup

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

434|33|Updated Jul 27, 2025
Search Tags:#automation#debugging#session-management#chrome#profile#dev-browser#remote-debugging
One-click install
npx skills add https://github.com/udecode/kitcn --skill browser-debug-setup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser-debug-setup
Source: https://github.com/udecode/kitcn/tree/main/.agents/skills/browser-debug-setup
Command: npx skills add https://github.com/udecode/kitcn --skill browser-debug-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

One-time setup for a persistent debugging browser on 127.0.0.1:9222 for dev-browser --connect. Use when browser work is needed but no reusable debug browser is running yet.

Core Features & Use Cases

  • Establish a dedicated Chrome profile for agent work (e.g., dev) and clone it into a separate user data dir, leaving the daily Default profile intact.
  • Launch a separate Chrome instance with remote debugging enabled on 127.0.0.1:9222 using a persistent user data directory.
  • Reuse the same debug browser for subsequent agent tasks to minimize prompts and ensure session continuity.
  • Provide macOS launch guidance to start Chrome with a dedicated profile without affecting existing windows.

Quick Start

Open a dedicated signed-in Chrome profile and start the persistent debug browser session using the steps above.

Frequently Asked Questions about browser-debug-setup

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

FAQPage Schema
How do I set up a persistent Chrome remote debugging session on macOS?▼

To set up persistent Chrome remote debugging on macOS, launch a separate Chrome instance using a dedicated user-data-dir and remote debugging port 127.0.0.1:9222, ensuring session continuity for agent work without affecting your daily profile.

Why do I need a dedicated user data directory for Chrome debugging?▼

A dedicated user data directory is needed for Chrome debugging to clone a separate profile, leaving your Default profile intact while maintaining consistent session state across human and agent interactions during repeated debugging sessions.

Can I reuse the same debugging browser for multiple agent tasks?▼

Yes, you can reuse the same debugging browser for subsequent agent tasks. By keeping one persistent debugging browser ready on port 9222, you minimize prompts and ensure reliable session continuity across tasks.

Does setting up remote debugging affect my existing Chrome windows?▼

No, setting up remote debugging does not affect existing Chrome windows. By applying macOS launch guidance to start Chrome with a dedicated profile and separate user data directory, your existing daily browser windows remain completely intact.

What is the best way to maintain a debugging profile for automation?▼

The best way to maintain a debugging profile for automation is to clone a dedicated Chrome profile into a separate user data directory and launch it with remote debugging enabled, ensuring consistent session state for repeated debugging.

How do I connect to a remote debugging port after launching Chrome?▼

After launching Chrome with remote debugging enabled on 127.0.0.1:9222, you connect to the remote debugging port using dev-browser --connect, allowing reliable agent interaction with the persistent debug browser session.

Related Skills

Explore More Software Engineering Skills→
eins78eins78
2

chrome-browser

Configure a dedicated Chrome for Testing environment with CDP on port 9222 for Playwright MCP.

Community
Intermediate
mynameistitomynameistito

electron

Automate Electron desktop apps via Chrome DevTools Protocol remote debugging ports.

Community
Intermediate
muklesmukles

browser-debug-setup

Establish a persistent Chrome debugging session on port 9222.

Community
Intermediate
konneh-hubkonneh-hub

vercel-sandbox

Run headless Chrome browser automation inside Vercel Sandbox microVMs.

Community
Advanced