Browser Automation with playwright-cli

Authentication → attach to the user's live Chrome. Any time a task needs a signed-in session (logging in, or reaching anything behind a login or bot challenge), use attach --extension=chrome to drive the user's real Chrome with its existing logins, instead of launching a fresh browser with open. Playwright-launched Chromium and WebKit get flagged by Google/OAuth as an insecure browser and the sign-in is blocked. See references/extension-attach.md.

House patterns (use these by default)

# One NAMED session per task (-s=dash, -s=mail, -s=print …); pass the same -s to every
# follow-up command. Parallel tasks never collide, and the default session stays clean.
playwright-cli -s=dash open https://dash.example.com

# Signed-in work: attach to the user's real Chrome. Token skips the "Share this tab" dialog.
PLAYWRIGHT_MCP_EXTENSION_TOKEN=<token> playwright-cli -s=mail attach --extension=chrome
# Stale attach session? close-then-reattach is the reliable reset:
playwright-cli -s=mail close 2>/dev/null; PLAYWRIGHT_MCP_EXTENSION_TOKEN=<token> playwright-cli -s=mail attach --extension=chrome

# Big pages: write the snapshot to a file and grep it, instead of dumping it into context
playwright-cli -s=dash snapshot --filename=.playwright-cli/cur.yml >/dev/null 2>&1
grep -n -iE 'button|save|error' .playwright-cli/cur.yml