Browser Automation
Browser automation is the underlying infrastructure on which every AI agent, scraper, and end-to-end test sits. The vocabulary is shared across a wide range of tools — Playwright, Puppeteer, Selenium, Stagehand, Notte — but the concepts are remarkably stable: headless versus headful execution, the Chrome DevTools Protocol, browser sessions and contexts, anti-bot detection and the fingerprinting signals it relies on, residential and datacenter proxies, parallel execution, and the boundaries between cloud, serverless, and self-hosted deployments. Understanding these primitives is the difference between an automation that works in development and one that survives production traffic and detection systems. This category collects the canonical definitions every developer touching the browser layer should know.
Common Questions
Other categories
Definitions and concepts for building, evaluating, and operating AI agents that drive a real browser.
Digital identities, credential vaults, 2FA, CAPTCHAs, and the patterns AI agents need to log in like a real user.
Wrap browser-driven work as callable Web APIs — the layer that exposes agent runs as durable, scheduled, schema-typed endpoints.
Scraping APIs, anti-scraping defenses, dynamic content, and the patterns for getting data off the modern web.
Structured extraction, LLM-ready content, schema-based parsing, and the formats AI systems consume.
Build your AI agent on the open web with Notte
Cloud browsers, agent identities, and the Anything API — everything you need to ship reliable browser agents in production.