0xplayerone/pi-browser-use
Managed persistent, fresh, and existing Chrome sessions with focus-safe browser tools and CLI-first skills.
Initialize or reauthenticate the managed persistent browser profile. Use on a new machine or plugin instance, at a login wall, or when SSO, 2FA, passkeys or provider verification require a human. Works with native Pi and portable MCP hosts.
Browser-use policy for agents. Use before any browser_* tool call. Prefer CLIs and APIs over browser automation, default to a dedicated persistent headless profile, use fresh mode for anonymous checks, and never steal user focus.
Turn observed browser traffic into a standalone API client. Use when a task repeats the same site interactions and should stop driving the browser — record the network calls, then replace clicks with fetch.
Exploratory testing playbook for bug hunts and quality passes. Use when asked to dogfood, poke at, or break a site — tour it with intent instead of clicking around.
Verify Gmail authentication in the persistent managed browser profile. Use when a task needs the Gmail inbox, after browser_setup, or when Google shows a login or verification challenge.
Decide when browser automation has hit its limits and hand off to a repo Playwright run instead. Use when a task needs request mocking, assertions, traces, repeatability, or CI parity that browser_* tools cannot provide.
Standard flow for diagnosing a broken page. Use when a site misbehaves, renders wrong, or throws — snapshot, console errors, failed network requests, then screenshot.
Screenshot discipline for visual checks of WebGL/canvas scenes and layouts. Use when asked whether something "looks right", for before/after comparisons, or for viewport coverage.