Skip to main content
Scrape (one URL, clean content), crawl (walk a site from a seed, stream every page), search (results you can act on, optionally rendered), browsers (a real browser your agent drives over plain CDP), and agents (hand over a task, it finishes in a real browser). Monitors watch a page on a schedule alongside them.
No. Live browser control needs a CDP connection held open in the caller’s own process, so it exists only in the TypeScript SDK. Python, the CLI and MCP reach the same underlying page work through agent and scrape, which run the loop on the platform’s own side instead.
A pinned exit and persistent storage that keeps a login across sessions, rather than signing in fresh every time. See profiles.
It asks, or a person takes the wheel. When a run needs something only you know, it pauses with the question on its status, and agent.answer resumes it from where it stopped. agent.control pauses the run with the browser still open and hands you a URL to drive directly; releasing it resumes the run on whatever page you left it on. See human in the loop.
No. No route sends a running agent new instructions. A person acts on a live run by answering a question it asked, or with control, taking the browser and handing it back; cancel stops it. None of them changes what it was asked to do.