OpenClaw

chrome-debug-launcher

Launch two independent Chrome browser instances — one normal and one with remote debugging enabled on port 9222. Activate when user says "打开两个浏览器", "开调试浏览器", "launch chrome debug", or any similar request to open a debug Chrome alongside a normal Chrome.

chengzongxin0 来源安装数☆ 0 仓库 Stars

查看来源 ↗安装与使用 SKILL.md ↗

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求，再添加到工作流。

SkillHub CLI

skillhub install chengzongxin/chrome-debug-launcher

打开来源仓库，查看说明和兼容环境后，按来源提供的命令或步骤安装。

将来源链接提供给你的 Agent，让它先读取说明、核对依赖，并向你说明将执行的安装步骤。

查看来源 ↗使用指南

技能说明

Chrome Debug Launcher

Launch two independent Chrome instances: one normal, one with remote debugging on port 9222.

Steps

Kill all Chrome processes
Launch normal Chrome (no extra args)
Wait 2 seconds, then launch debug Chrome

Commands by Platform

Windows (PowerShell)

# Step 1: Kill Chrome
taskkill /F /IM chrome.exe /T 2>$null
Start-Sleep -Seconds 2

# Step 2: Normal Chrome
Start-Process "C:\Program Files\Google\Chrome\Application\chrome.exe"

# Step 3: Debug Chrome (after 2s)
Start-Sleep -Seconds 2
Start-Process "C:\Program Files\Google\Chrome\Application\chrome.exe" -ArgumentList '--remote-debugging-port=9222', '--user-data-dir=C:\selenum\ChromeProfile'

macOS (bash)

# Step 1: Kill Chrome
pkill -f "Google Chrome" 2>/dev/null; sleep 2

# Step 2: Normal Chrome
open -a "Google Chrome"

# Step 3: Debug Chrome (after 2s)
sleep 2
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \
  --remote-debugging-port=9222 \
  --user-data-dir="$HOME/selenium/ChromeProfile" &

Result

Instance 1: Normal Chrome, default profile, regular use
Instance 2: Debug Chrome, port 9222, isolated user data dir
- Connect via Selenium/Playwright: http://localhost:9222

来源信息

Source: github
Repository: openclaw/skills
Path: skills/chengzongxin/chrome-debug-launcher
Version: —
Commit: cc497941777cd7dd7f3536258333306ae32d2133
分类来源: rules
状态: active
可见性: public

这些信息来自收录时的来源分析，可能滞后；使用前请核对最新来源文件。

来源内容

SKILL.md

# Chrome Debug Launcher

Launch two independent Chrome instances: one normal, one with remote debugging on port 9222.

## Steps

1. **Kill all Chrome processes**
2. **Launch normal Chrome** (no extra args)
3. **Wait 2 seconds**, then launch debug Chrome

## Commands by Platform

### Windows (PowerShell)

```powershell
# Step 1: Kill Chrome
taskkill /F /IM chrome.exe /T 2>$null
Start-Sleep -Seconds 2

# Step 2: Normal Chrome
Start-Process "C:\Program Files\Google\Chrome\Application\chrome.exe"

# Step 3: Debug Chrome (after 2s)
Start-Sleep -Seconds 2
Start-Process "C:\Program Files\Google\Chrome\Application\chrome.exe" -ArgumentList '--remote-debugging-port=9222', '--user-data-dir=C:\selenum\ChromeProfile'
```

### macOS (bash)

```bash
# Step 1: Kill Chrome
pkill -f "Google Chrome" 2>/dev/null; sleep 2

# Step 2: Normal Chrome
open -a "Google Chrome"

# Step 3: Debug Chrome (after 2s)
sleep 2
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \
  --remote-debugging-port=9222 \
  --user-data-dir="$HOME/selenium/ChromeProfile" &
```

## Result

- **Instance 1**: Normal Chrome, default profile, regular use
- **Instance 2**: Debug Chrome, port 9222, isolated user data dir
  - Connect via Selenium/Playwright: `http://localhost:9222`

搜索