What problem does it solve?
It removes the guesswork of inspecting or debugging a webpage by letting you query and control the exact page the user currently has open in their local Chrome session.
Core Features & Use Cases
- Enumerate and target open pages: List available Chrome DevTools Protocol targets and pick the right one by prefix, which fits workflows where multiple tabs/windows are open.
- Read structure and content: Capture accessibility snapshots or extract full page HTML, including targeted DOM HTML via CSS selectors.
- Interact and troubleshoot UI: Navigate to URLs, click or click-by-coordinates, type text, and visually verify results with screenshots that include coordinate mapping.
- Debug page behavior: Evaluate JavaScript in the page context, fetch network resource timing summaries, and load “load more” sections by repeatedly clicking until content disappears.
- Use case: When a user says “the button isn’t working on this page,” you can list the tab, snapshot the accessible UI, click the control, capture a screenshot, and then evaluate a targeted expression to confirm the state.
Quick Start
Ask to use live Chrome by saying: Inspect my open Chrome page and capture a visual screenshot of the current layout, then click the element matching the selector #submit and show what changed.