Stable Browser

Set up reliable browser automation using Chrome DevTools Protocol (CDP) instead of the flaky browser extension relay. Use when browser relay keeps disconnect...

This skill appears coherent and implements what it promises, but review and consider the following before running: - Inspect scripts before running: scripts/setup-cdp.sh is local and will create ~/.chrome-debug-profile, update ~/.openclaw/openclaw.json, and on macOS create/load ~/Library/LaunchAgents/com.openclaw.chrome-cdp.plist. - Persistence: the LaunchAgent auto-starts Chrome at login (user-level). If you don't want that, skip the LaunchAgent step or remove the plist after setup. - Profile/cookies: you will be asked to log into sites in the new profile; session cookies and tokens will be stored under ~/.chrome-debug-profile. Treat that directory as sensitive and back it up or delete it if you no longer need persistent sessions. - Platform note: the included setup script assumes macOS Chrome path; on Linux/Windows you should follow the manual-setup instructions instead or edit the script to point to your Chrome binary. - Process killing: the script uses pkill -f 'remote-debugging-port=9222' if port is in use; this may terminate other processes that were using that flag—verify before running on shared systems. - Headless flags: the documentation shows using --no-sandbox for CI/headless. Be cautious: --no-sandbox reduces security and should only be used in controlled CI environments. - Network exposure: the CDP endpoint is bound to 127.0.0.1 in these instructions (local only). Ensure you do not expose the debug port to other hosts if you want to keep it local. If you're comfortable with the above and only want a dedicated, local CDP-backed browser for automation, this skill appears appropriate. If you need higher assurance, run the script line-by-line manually and verify the created files and LaunchAgent before enabling it.

Type: OpenClaw Skill Name: stable-browser Version: 1.0.0 The skill bundle is benign. It sets up a dedicated Chrome instance for OpenClaw's browser automation via the Chrome DevTools Protocol (CDP). The `scripts/setup-cdp.sh` script launches Chrome with a debug port, creates a dedicated user profile (`~/.chrome-debug-profile`), updates the local OpenClaw configuration (`~/.openclaw/openclaw.json`), and establishes a macOS LaunchAgent (or provides systemd instructions for Linux) to ensure Chrome auto-starts and persists. All actions, including file system modifications and persistence mechanisms, are explicitly stated in `SKILL.md` and are directly aligned with the skill's stated purpose of providing a stable browser connection. There is no evidence of data exfiltration, unauthorized remote execution, obfuscation, or prompt injection attempts to subvert the agent for malicious ends.