browser-controllisted

# browser-control Use `sagui browser` to inspect and automate Chromium pages through the Chrome DevTools Protocol (CDP). Treat this as a browser-only environment: it never falls back to native macOS automation. ## Preflight Run these checks before browser automation: ```bash uname -s command -v sagui sagui browser --help ``` Stop if the platform is not macOS. If `sagui` is missing, or the installed version has no `browser` command, ask before installing or upgrading it: ```bash brew update brew install NakaokaRei/tap/sagui # Use this instead when sagui is already installed: brew upgrade NakaokaRei/tap/sagui ``` Do not claim that Accessibility or Screen Recording permission is required for browser-only CDP actions. Those permissions apply to native `sagui` commands, not `sagui browser`. ## Connect to Chromium List tabs on the default loopback endpoint: ```bash sagui browser tabs ``` If no debugging endpoint is available, ask the user to start a dedicated Chromium profile, or obtain approval before launching it: ```bash "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" \ --remote-debugging-address=127.0.0.1 \ --remote-debugging-port=9222 \ --user-data-dir=/tmp/swift-auto-gui-browser-profile ``` Keep the endpoint on loopback. Do not expose or connect CDP to a LAN or public address. The browser session does not launch Chromium, manage profiles, bypass login, solve CAPTCHA, or handle 2FA. Use the target ID printed by `sagui browser tabs` when a spe