| name | patchright-cli |
| description | Interactive browser automation through Patchright and real Google Chrome. Use when an agent needs to browse, inspect, interact with, screenshot, or debug web pages with a headful browser that avoids the stock Playwright/CDP automation shape many sites detect. |
Patchright CLI
Use patchright-cli for Patchright-first browser automation with real Google Chrome.
The command surface mirrors playwright-cli: read the Playwright CLI skill as the command reference, then replace playwright-cli with patchright-cli. This keeps the familiar Playwright-style workflow for navigation, snapshots, clicks, typing, screenshots, tracing, storage state, videos, request controls, and custom page code while using Patchright as the browser driver.
Primary reference:
skills/playwright-cli/SKILL.md
Detailed references:
skills/playwright-cli/references/element-attributes.md
skills/playwright-cli/references/request-mocking.md
skills/playwright-cli/references/running-code.md
skills/playwright-cli/references/session-management.md
skills/playwright-cli/references/storage-state.md
skills/playwright-cli/references/tracing.md
skills/playwright-cli/references/video-recording.md
Quick Start
patchright-cli open
patchright-cli goto https://example.com
patchright-cli snapshot
patchright-cli click e3
patchright-cli type "search query"
patchright-cli screenshot
patchright-cli close
Rule
Use patchright-cli the same way as playwright-cli.
Do not add setup steps or browser-selection flags for normal use; the runtime wrapper always uses the built-in Google Chrome installation and launches headful sessions by default. Browser install commands and alternate browser choices such as Chromium, Firefox, or WebKit are not part of this runtime contract.
This is an agent-facing interactive browser CLI contract, not a signal to use Patchright or Playwright as a workspace Node package or test runner.
When following Playwright CLI examples:
playwright-cli goto https://example.com
run:
patchright-cli goto https://example.com