This guide covers both Stagehand SDK v4 and v3. v4 runs as a Chrome extension alongside the browser rather than driving it purely over CDP, so a remote Kernel browser needs the extension loaded into it — the version tabs below show each setup. To move between versions, see the Stagehand migration guide. The CLI template uses v4.
Quick start with the Stagehand template
The fastest way to run Stagehand on Kernel is our app template, which comes pre-wired for v4:index.ts— the automation (searches a startup on Y Combinator and extracts its team size).stagehand-extension.ts— a helper that loads the Stagehand extension onto the Kernel browser.
MODEL and its API key in a .env file:
.env
Adding Kernel to an existing Stagehand project
If you already have a Stagehand implementation, switch it to Kernel’s cloud browsers by updating your browser setup. The steps differ between v4 and v3 — pick your version below.- Stagehand v4
- Stagehand v3
1. Install the Kernel SDK2. Load the Stagehand extension onto the Kernel browserStagehand v4 runs as a Chrome extension. When 3. Create a browser and connectCreate a Kernel browser, load the extension, then connect Stagehand to its CDP URL:4. Use your Stagehand automationDrive the page with Stagehand’s primitives. Note the v4 API: page access is async (5. Clean upStagehand v4 only closes browsers it launched, so close the connection and delete the Kernel browser yourself. Nest the cleanup so a failed
localBrowser.connect is called without an extensionId, Stagehand loads the extension into the running browser over CDP (Extensions.loadUnpacked), reading it from a path on the browser’s filesystem. Mirror the extension — shipped inside the @browserbasehq/stagehand package — onto the running Kernel browser at that exact path first:activePage()), and extract returns its result under data:close() never skips deleting the browser:Benefits of using Kernel with Stagehand
- No local browser management: Run automations without installing or maintaining browsers locally
- Scalability: Launch multiple browser sessions in parallel
- Stealth mode: Built-in anti-detection features for web scraping
- Session state: Maintain browser state across runs via Profiles
- Live view: Debug your automations with real-time browser viewing
Next steps
- Check out live view for debugging your automations
- Learn about stealth mode for avoiding detection
- Learn how to properly terminate browser sessions
- Learn how to deploy your Stagehand app to Kernel