Playwright Cli

playwright-cli open https://example.com
playwright-cli open https://example.com --headed
playwright-cli -s=myapp open https://example.com
playwright-cli snapshot
playwright-cli click e12
playwright-cli fill e15 "hello"
playwright-cli press Enter
playwright-cli screenshot
playwright-cli console
playwright-cli network
playwright-cli close

Session tips

• Use playwright-cli -s=<name> ... to isolate work by app or task.
• Reuse the same session for multi-step authenticated flows.
• Use playwright-cli list to inspect active sessions.

Good defaults

• Start with open, then snapshot.
• Do not invent flags or combine unsupported subcommand options; for example, playwright-cli open does not support --snapshot.
• After actions that may change the page, take another snapshot before using new refs.
• Prefer concise command sequences over long exploratory loops.
• Use screenshot when the result should be preserved or shown.

Example prompt behavior

For a request like "test the login flow", use commands like:

playwright-cli -s=login open https://app.example.com/login --headed
playwright-cli -s=login snapshot
playwright-cli -s=login fill e12 "[email protected]"
playwright-cli -s=login fill e15 "password"
playwright-cli -s=login click e18
playwright-cli -s=login snapshot
playwright-cli -s=login screenshot