kernel-browser-pools
Browser Pools
Pre-warmed browser instances for fast acquisition. Ideal for high-throughput automation.
Note: Unless otherwise noted,
idarguments refer to the browser session ID, not invocation IDs returned by Kernel commands.
When to Use
Browser pools are ideal when you need to:
- Minimize latency for browser acquisition with complex configurations (profiles, proxies, extensions)
- Run many short-lived browser tasks in parallel with consistent startup times
- Maintain consistent browser configuration across multiple sessions
- High-throughput automation where browser creation overhead impacts performance
- Parallel scraping of many pages with identical browser settings
For one-off or long-running browser sessions, creating browsers directly with kernel browsers create may be simpler.
Prerequisites
More from kernel/skills
kernel-agent-browser
Best practices for using agent-browser with Kernel cloud browsers. Use when automating websites with agent-browser -p kernel, dealing with bot detection, iframes, login persistence, or needing to find Kernel browser session IDs and live view URLs.
347kernel-cli
Complete guide to Kernel CLI - cloud browser platform with automation, deployment, and management
295kernel-typescript-sdk
Build browser automation scripts using the Kernel TypeScript SDK with Playwright, CDP, and remote browser management.
271kernel-python-sdk
Build browser automation scripts using the Kernel Python SDK with Playwright and remote browser management.
255kernel-auth
Setup and manage Kernel authentication connections for any website (Gmail, GitHub, Outlook, or custom domains). Handles managed auth flows with automatic reauthentication support.
246profile-website-bot-detection
Profile a website for bot detection vendors using stealth vs non-stealth Kernel browsers. Use when analyzing bot detection on a website, comparing stealth effectiveness, identifying anti-bot vendors and products, or detecting challenge types.
219