Agent skill · software engineering · steipete
browser-use
Control the user's existing signed-in Chrome: callable Codex Chrome plugin first, then OpenClaw extension-backed mcporter, with direct DevTools attachment only as a last fallback.
Why this skill is useful
Adds specific commands and workflows for Chrome automation that the AI wouldn't reliably generate on its own.
What it needs
Requires mcporter, openclaw installed locally. About 9k tokens when loaded. Last updated 2026-08-06. 6,510 stars on the source repository.
What this skill does
Browser Use Control the user's existing real Chrome profile, especially for login-dependent work and live UI verification. Route 1. Use the Codex Chrome or Chrome [Internal] plugin when it is callable in the active session. Installed on disk is not enough. 2. Otherwise prefer the OpenClaw extension-backed mcporter route. 3. Use legacy direct DevTools attachment only as the explicit last fallback. For mcporter, the MCP call remains the agent-facing control interface. The OpenClaw extension is the transport underneath it, not a separate tool. Set chromeDevtoolsRelay: "require" on the canonical global Chrome server definition to enforce relay-only routing. Keep the caller policy explicit as well: Seeing an agent request the chrome-devtools MCP tool is therefore expected. A Chrome Allow remote debugging? prompt or a relay-policy error indicates that the extension transport was not used. The shared daemon retains canonical policy; a shell environment prefix alone cannot change that policy. Never use isolated Chrome, the Codex in-app browser, Playwright, Puppeteer, AppleScript, osascript, generic GUI scripting, or macOS open as a browser-control substitute unless the user explicitly asks for an isolated or new browser. Peekaboo is allowed only for Chrome or extension setup and visible prompts. Login-heavy sites often depend on the real profile's cookies, SSO, device trust, and extensions. For a rendered-browser bug, prove behavior through this real profile. Treat curl, source inspection, API checks, and isolated test browsers as supporting evidence, not substitutes for live UI proof. Extension Relay Model OpenClaw creates a random per-host relay key in its mode-0600 credentials directory. The extension and same-host clients use nonce-bound mutual HMAC proofs. The reusable key is never sent to an unverified loopback listener, placed in a URL, or passed to the child MCP process. Keep credentials out of configuration, command output, chat, logs, and screenshots. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills steipete/browser-use