agent-browser

Topics in the source

• Agent Browser
• When to use
• When not to use
• Before launching the browser
• Driving the browser
• What evidence to record
• Login-gated pages
• Performance and politeness

Use a controlled browser to verify behavior, capture evidence, or extract information from web pages that a static fetch cannot reach (SPAs, login-gated pages, dynamic content). This skill is about supervised verification, not unattended scraping. You need a screenshot of a deployed page or a local dev server to confirm a UI change. You need to read JavaScript-rendered content that curl/wget will not see. A user reports a UI bug and you need to reproduce it interactively to capture console errors, network requests, or layout state. You need to walk through a short flow (load page, click, observe) to verify acceptance criteria. The page is reachable as static HTML. Use curl/HTTP fetch — it is cheaper, faster, and more reliable. The task is unattended large-scale scraping. That belongs to a dedicated scraper with rate limits, robots.txt handling, and a real user agent policy — not this skill. The site is behind authentication you do not own credentials for, or whose terms of service prohibit automation. The site involves sensitive accounts (banking, healthcare, government) where automation risks lockout or compliance issues. Confirm the URL and what state should be true after navigat

This is an excerpt. Refer to the complete source and its current requirements.