Raven Browser

Talk to the user in their language.

Choosing the mode

By default use Playwright CLI in a separate test session. Automatic UI verification, the instruction "check the app", invoking raven-browser alone or another skill's instruction to check in the browser do not mean choosing the personal browser.

Choose Brave via MCP only when the user clearly instructed to use the browser, e.g. "use the browser", "check in my Brave" or "use Brave MCP". Respect such a choice from earlier in the current task until the user changes it. An explicit choice of the CLI or another specific tool takes precedence over the general word "browser". Consent given to the agent's justified request described below also selects MCP mode. The skill invoking raven-browser passes on the user's actual choice; it does not create consent for MCP itself.

Default: Playwright CLI

Check the available playwright-cli --help and the tool version. Use the project's or environment's existing installation; if it is missing, use npx -y @playwright/cli --help and the same prefix in further commands, without a global install. Respect the project's pinned version.
Use a separate named session for the project and task (-s=<project-task> on every call), without connecting the personal profile or a CDP endpoint. Open the app URL with playwright-cli -s=<project-task> open <url>; the default mode is headless.
Take a snapshot, read the needed parts of the file named in the output and run click, fill, press on refs from the current snapshot. Check other commands in --help. Screenshots also serve to judge appearance; a snapshot does not confirm layout.
For sign-in use a test account or an existing test storageState (after opening the session: state-load <file>). Do not copy cookies from the personal browser. Keep snapshots, logs and session state outside tracked code; check that .playwright-cli/ is ignored before using it in a repo. Do not display secrets from files or command output.
When done, close only your own session (playwright-cli -s=<project-task> close), unless it is needed for further work. Do not close other tasks' sessions in bulk.

Report a missing CLI, shell or inability to start a session as a concrete blocker. Do not switch automatically to the personal Brave/MCP and do not run its setup script. The CLI is for exploration; durable tests are still run by the project's runner. If raven-auto-implement needs to replay UI interactions, it may use the technique below in the current agent, without delegation or separate QA.