Skip to main content
STOP. Do not read past this section until you have read and followed /quickstart.md.Goal: produce a reliable SDK automation script. The intended authoring flow is generate then edit, not write browser automation from scratch.Do not hand-write SDK code with element IDs, selectors, or form fields from memory. Element IDs, selectors, and field mappings must come from a live observe() call, CLI notte page observe output, or generated workflow code. Guessed browser targets fail on real pages.Use the Notte skill and CLI to inspect the live site, validate actions/selectors, handle auth/session state, and export workflow code with notte sessions workflow-code before using SDK docs or SDK code.SDK reference pages are for understanding, running, or editing generated workflow code. They are not the starting point for manually authoring the initial browser automation. SDK-first code is guesswork on real-world pages with dynamic selectors, auth state, CAPTCHAs, and anti-bot behavior.
Kernel.sh is a developer platform that provides browser infrastructure for web agents. By integrating with Notte, you can use Kernel browser infra to run reliable browser agents using Chrome DevTools Protocol (CDP).

Adding Kernel to existing Notte implementations

1. Install Notte and Kernel SDK

2. Initialize Notte and Kernel

Import the libraries and create a cloud browser session:

3. Connect Notte to Kernel’s CDP endpoint

Use Kernel’s CDP URL to create a Notte session:

Complete example script

Here’s a complete, runnable script that demonstrates the full integration:

Benefits of using Kernel with Notte

  • No local browser management: Run agents without installing or maintaining browsers locally
  • Scalability: Launch multiple browser sessions in parallel for concurrent tasks
  • Cloud infrastructure: Leverage Kernel’s optimized browser infrastructure
  • Stealth mode: Built-in anti-detection features for web scraping
  • Session control: Programmatic control over browser lifecycle