browser▌

sentry-browser-sdk

Minimal Chrome DevTools Protocol (CDP) helpers for browser automation without MCP server setup.

Build browser extensions for Chrome, Firefox, and cross-browser platforms using Manifest V3 architecture. \n \n Covers extension structure, Manifest V3 configuration, content scripts, background service workers, popup UIs, and storage patterns \n Includes communication patterns between popup, background worker, and content scripts; DOM injection and event handling on web pages \n Provides Chrome Storage API usage with async/await patterns, storage limits, and data persistence across devices \n H

Browser automation with persistent page state across sequential scripts. \n \n Two modes: standalone Chromium (default) or extension mode connecting to user's existing Chrome browser with authentication already in place \n Discover page elements via ARIA snapshot accessibility tree, then interact using element references; alternatively read source code to write direct selectors \n Small, focused scripts that run incrementally—each script does one action (navigate, click, fill, check), then you e

Fast Rust-based headless browser automation with real Chrome profile and session support. \n \n Supports headless Chromium, real Chrome with profile/OAuth reuse via Chrome DevTools Protocol, and persistent session cookies for logged-in workflows \n 30+ commands covering navigation, interaction (click, type, fill, drag, upload), extraction (text, HTML, attributes, screenshots), and state checks \n Deterministic element selection via snapshot refs (@e1, @e2, etc.) and semantic finders (role, text,

Vision-driven browser automation from screenshots, no DOM access required. \n \n Operates in a headless Puppeteer browser that persists across CLI calls, allowing sequential commands without session loss \n Interacts with all visible page elements using natural language prompts; no CSS selectors or accessibility labels needed \n Requires configuration of a vision-capable model (Gemini, Qwen, Doubao, or similar) via environment variables for visual grounding \n Supports connect, take_screenshot,

Cloud browser automation for sandboxed agents without local GUI access. \n \n Supports navigation, page inspection, interactions, JavaScript execution, and cookie management via 30+ CLI commands \n Includes cloud session management for running autonomous browser agents in parallel, with task monitoring and structured output options \n Provides local dev server tunneling via Cloudflare to expose ports from the remote machine to the cloud browser \n Maintains session state across commands, enablin

If next-browser is not already on PATH, install @vercel/next-browser globally with the user's package manager, then playwright install chromium.

Take focused screenshots of specific regions on web pages — a Reddit post, a tweet, an article section, a chart, etc. — not just a full-page dump.

Browser automation with local Chrome or remote Browserbase for protected sites, bot detection, and CAPTCHAs. \n \n Two modes: local Chrome (default, no setup) or remote Browserbase (anti-bot stealth, automatic CAPTCHA solving, residential proxies, session persistence) \n Core commands cover navigation, page inspection, interaction (click, type, fill, select, drag), and session management via CLI \n Use browse snapshot to read the accessibility tree and get element refs for reliable interactions;