Skip to main content
Kernel’s browsers are compatible with all browser and Computer Use frameworks.

Universal CDP compatibility

Kernel browsers work with any framework or tool that supports the Chrome DevTools Protocol (CDP). This means you can:
  • Use any agent framework: Integrate with popular frameworks like Browser Use, Stagehand, Playwright, Puppeteer, Selenium, and more
  • Connect via CDP: All browsers expose a CDP WebSocket URL for direct connection
  • No vendor lock-in: Switch between frameworks or use multiple frameworks simultaneously
  • Standard protocols: Built on open standards that work with the entire browser automation ecosystem

Computer Use

For vision-language models (VLMs) that predict browser actions from screenshots, Kernel provides Computer Controls APIs that enable direct mouse, keyboard, and screen interactions. These low-level controls let you:
  • Capture screenshots to send to your VLM
  • Execute predicted actions (clicks, typing, scrolling, dragging)
  • Build custom agentic loops with any VLM provider
This approach works with any computer use model, including Anthropic Claude, OpenAI CUA, Google Gemini, and others.

Integrations by Kind

Agent frameworks
  • Browser Use — AI browser agent framework
  • Stagehand — AI browser automation with natural language
  • Hermes Agent — run Hermes browser tools on Kernel browsers
  • Vibium — WebDriver BiDi client
Coding agents and harnesses Computer use models Credentials and payments
  • 1Password — use credentials from your own vaults for managed auth
  • Payments — provider-backed payments without exposing card data
Deployment and runtimes
  • Vercel — deploy browser automations to Vercel
  • Val Town — serverless function runtime
  • Terraform — manage durable Kernel infrastructure as code
Provisioning and billing
  • Stripe Projects — provision Kernel plans and API keys via the Stripe Projects CLI
Observability
  • Laminar — tracing for AI browser automations

Custom Integrations

Kernel works with any tool that supports CDP. See how you drive the browser to pick a control surface, and the control guide for connecting any other framework. Automating a specific website reliably is usually a skill, not an integration — see site-specific skills.