What problem does it solve? Automating tasks that depend on existing Chrome state—open tabs, logged-in sessions, or installed extensions—requires direct browser control, which generic APIs and connectors cannot provide. ## Core Features & Use Cases - Browser Selection & Binding: Select the in-app browser or Chrome based on explicit user requests, target URLs, or runtime defaults, with persistent bindings reused across turns. - Page Automation: Navigate pages, click elements, type input, take screenshots, and read visible page state through the browser-client runtime. - Troubleshooting Guidance: Built-in documentation topics for bootstrap failures and Chrome extension setup or communication issues. - Use Case: A user asks to fill out a form on a site where they are already logged in; the Skill connects to their Chrome session, navigates to the page, and completes the form using the existing authenticated state. ## Quick Start Connect to my Chrome browser and open the current tab to check whether I am signed in to my account.