browser
Browser
Use Chrome DevTools MCP for the requested browser task. Stay within the requested scope; use the existing MCP connection.
Site-specific context
Use site or repository instructions supplied by the caller. If the caller provides a path, read it and apply only the matching instructions. If a wrapper has already loaded matching context, use that context. Do not search fixed user paths or infer site rules from unrelated files. Without supplied context, use the generic workflow below.
Match the requested URL, repository, or named app, not unrelated open tabs. Recheck matches before switching sites. If supplied instructions are missing or conflict, ask before proceeding.
1. Establish target and baseline
Use the user's target URL, otherwise the matching local instructions or the repository's documented dev URL. Ask if none is clear. Confirm reachability and required context; report blockers rather than guessing another environment.
Before changing source code or performing the test interaction, record relevant console errors/warnings with message, source/stack, and occurrence counts. For navigation/load tests, capture from before navigation. For regression checks, reproduce the same journey on the unchanged version when available; an idle-page baseline alone cannot establish that interaction errors are new.
Keep baseline evidence separate from later runs. Compare equivalent context, actions, and observation windows.