- name
- super-browser
- description
- Browser automation through the published
@pzeda/super-browserpackage and itssuper-browserCLI against a real local Chrome session. Use when the task needs to open a webpage, inspect rendered content, click through a real site flow, reuse an existing Chrome login session, upload files, take screenshots, inspect network requests, or drive browser decisions and crawls. - metadata
- openclaw
- requires
- bins
super-browser Skill
Use the published @pzeda/super-browser package. Do not rely on repository-only scripts or src/ paths when performing browser work through this skill.
Setup
Require:
- Node.js 22+
- Chrome or Chromium installed locally
- A Chrome session that can expose CDP on port
9222
Install the package:
npm install -g @pzeda/super-browserThis installs the executable as:
super-browserCheck that the CLI is available:
super-browser --versionIf a global install is not appropriate, use:
npx -y @pzeda/super-browser --helpWhen To Use
Use this skill when the task needs a real browser session at all, especially for:
- opening a website or visiting a URL
- clicking, searching, paginating, or filling a browser flow
- inspecting what a page actually renders in Chrome
- reusing the user's logged-in Chrome session
- uploading files or taking screenshots in a browser
- inspecting browser-side network requests
- collecting structured page state for a decision-making workflow
Standard Rule
Do not lead with daemon management in the normal path.
For ordinary browser tasks, run the browser command you need directly, for example:
super-browser new --url https://example.comThe CLI auto-starts and reuses the daemon in the background.
Only switch into explicit connection diagnosis when browser commands fail or when browserConnected is reported as false.
Preferred diagnosis entrypoint:
super-browser doctorUse super-browser daemon status only as an advanced status check.
Core Workflow
When the task needs to use the browser, follow this order:
- Ensure
super-browseris available. - Run the actual browser command you need. Let the CLI auto-start the daemon.
- If browser connection fails, run
super-browser doctor. - Create and use a dedicated task tab.
- Reuse the returned
pageIdfor later commands. - Prefer structured commands over ad hoc browser scripts.
Create a task tab:
super-browser new --url https://example.comNavigate:
super-browser navigate --page <pageId> --url https://example.com/search?q=phoneInspect page state:
super-browser page-state --page <pageId>List managed tabs:
super-browser pagesClose the task tab:
super-browser close --page <pageId>Common Commands
Basic page operations:
super-browser info --page <pageId>
super-browser click --page <pageId> "button.search"
super-browser click-real --page <pageId> "input[type=file]"
super-browser scroll --page <pageId> --direction down --distance 3000
super-browser screenshot --page <pageId> --file D:\\ emp\\shot.png
super-browser upload --page <pageId> --selector "input[type=file]" --files D:\\ mp\\a.pdf D:\\ mp\\b.pdfNetwork inspection:
super-browser network start --page <pageId>
super-browser network requests --page <pageId> --business
super-browser network patterns --page <pageId>
super-browser network stop --page <pageId>Decision workflow:
super-browser decision candidates --page <pageId> --intent search --target "iphone"
super-browser decision propose --page <pageId> --intent search --target "iphone"
super-browser decision context --page <pageId> --intent search --target "iphone"
super-browser decision render --page <pageId> --intent search --target "iphone"
super-browser decision execute --page <pageId> --intent search --target "iphone"