Quickstart

Pick the way in that matches how you work. The first two are walked through on this page; the rest open their own guides.

Hand it to your coding agent

Copy one prompt into Cursor, Claude Code, or Codex and let it set up KERNEL.

Write it with an SDK

Create and drive your first browser in TypeScript, Python, or Go.

Call the REST API

Call KERNEL over HTTP from any language, starting with creating a browser.

Use the CLI

Create, drive, and debug browsers from a terminal.

Connect over MCP

Give any MCP client, like Claude or Cursor, a cloud browser as a set of tools.

Add Agent Skills

Teach your coding agent the KERNEL CLI, SDKs, and auth with one install.

Use your framework

Guides for the agent frameworks, models, and platforms you already use.

Follow a cookbook

Clone an end-to-end recipe and adapt it to your task.

Path 1: hand it to your coding agent

Copy this prompt into Claude Code, Codex, Cursor, or any agent that can run terminal commands. It installs the KERNEL CLI, signs you in, and opens a live view of a KERNEL browser that you or your agent can drive. From there, ask your agent to do a task on a site you care about.

See what this prompt does

Checks for the KERNEL CLI and installs or upgrades it with Homebrew.
Checks whether you’re signed in, and if not, runs kernel login and waits for you to finish signing in.
Creates a browser and opens its live view so you can watch it.

It stops and asks you for help if any step fails.

Agent-readable surfaces

Surface	What it’s for
`kernel.sh/llms.txt`	Hand-written. What KERNEL is, when to use it, every machine endpoint. Start here.
`kernel.sh/docs/llms.txt`	Index of every docs page, for fetching the ones a task needs.
`kernel.sh/docs/llms-full.txt`	The whole docs corpus in one file, for agents with room for it.
Agent Skills	KERNEL know-how installed into the agent, so it doesn’t re-read docs every session.
MCP server	KERNEL’s API as tools, for agents that call tools instead of writing code.
OpenAPI 3.1	For generating a client or calling the REST API directly.

Path 2: write it yourself with an SDK

Set your API key

Create an API key in the dashboard and set it as KERNEL_API_KEY. Every SDK, the CLI, and the MCP server read it from the environment.

export KERNEL_API_KEY=<your-api-key>

Install an SDK

npm install @onkernel/sdk

pip install kernel

go get github.com/kernel/kernel-go-sdk

Create a browser and drive it

This creates a browser, runs Playwright code inside the browser’s VM, returns the result, and cleans up. No local Chromium, no CDP connection to manage.

import Kernel from '@onkernel/sdk';

const kernel = new Kernel();

const browser = await kernel.browsers.create({ timeout_seconds: 300 });
console.log('live view:', browser.browser_live_view_url);

try {
  const { result } = await kernel.browsers.playwright.execute(browser.session_id, {
    code: `
      await page.goto('https://news.ycombinator.com');
      return await page.$$eval('.titleline > a', (as) => as.slice(0, 5).map((a) => a.textContent));
    `,
  });
  console.log(result);
} finally {
  await kernel.browsers.deleteByID(browser.session_id);
}

from kernel import Kernel

kernel = Kernel()

browser = kernel.browsers.create(timeout_seconds=300)
print("live view:", browser.browser_live_view_url)

try:
    response = kernel.browsers.playwright.execute(
        browser.session_id,
        code="""
          await page.goto('https://news.ycombinator.com');
          return await page.$$eval('.titleline > a', (as) => as.slice(0, 5).map((a) => a.textContent));
        """,
    )
    print(response.result)
finally:
    kernel.browsers.delete_by_id(browser.session_id)

package main

import (
	"context"
	"fmt"

	"github.com/kernel/kernel-go-sdk"
)

func main() {
	ctx := context.Background()
	client := kernel.NewClient()

	browser, err := client.Browsers.New(ctx, kernel.BrowserNewParams{
		TimeoutSeconds: kernel.Int(300),
	})
	if err != nil {
		panic(err)
	}
	defer client.Browsers.DeleteByID(ctx, browser.SessionID)
	fmt.Println("live view:", browser.BrowserLiveViewURL)

	res, err := client.Browsers.Playwright.Execute(ctx, browser.SessionID, kernel.BrowserPlaywrightExecuteParams{
		Code: `
			await page.goto('https://news.ycombinator.com');
			return await page.$$eval('.titleline > a', (as) => as.slice(0, 5).map((a) => a.textContent));
		`,
	})
	if err != nil {
		panic(err)
	}
	fmt.Println(res.Result)
}

Open browser_live_view_url while it runs and you’ll watch the page load.

Next steps

Two things determine the shape of everything after this: which control surface you use, and where your loop runs. How you drive the browser covers both.

Getting blocked?

Stealth and proxies to get past bot detection.

Behind a login?

Fill credentials from a vault, or let managed auth log in.

Need to pay?

Complete checkouts without exposing card data to your agent.

Want a worked example?

End-to-end recipes you can clone and run.

Overview

Start building

How it works

Partnering with KERNEL

Hand it to your coding agent

Write it with an SDK

Call the REST API

Use the CLI

Connect over MCP

Add Agent Skills

Use your framework

Follow a cookbook

Path 1: hand it to your coding agent

Path 2: write it yourself with an SDK

Next steps

Getting blocked?

Behind a login?

Need to pay?

Want a worked example?

Hand it to your coding agent

Write it with an SDK

Call the REST API

Use the CLI

Connect over MCP

Add Agent Skills

Use your framework

Follow a cookbook

​Path 1: hand it to your coding agent

​Path 2: write it yourself with an SDK

​Next steps

Getting blocked?

Behind a login?

Need to pay?

Want a worked example?

Path 1: hand it to your coding agent

Path 2: write it yourself with an SDK

Next steps