#Kernel Documentation Single Markdown

Name: Kernel Documentation Dataset
Creator: Kernel

Kernel is a developer tool with comprehensive developer documentation. The full documentation spans 165 pages and 432 KB, last crawled 3 weeks ago. This page reflects the latest available version.

Kernel / latest

165 pages·421.9 KB·updated Mar 23, 2026

### preview

----
url: https://www.kernel.sh/docs/auth/profiles
----

Profiles let you capture browser state created during a session (cookies and local storage) and reuse it in later sessions. This is the primitive to instantiate [authenticated browsers](https://www.kernel.sh/docs/auth/overview).

## [](#1-create-a-profile)1. Create a profile

Managed Auth automatically creates browser profiles for each [connection](https://www.kernel.sh/docs/auth/overview) you successfully authenticate. You can also use profiles without Managed Auth. The first step in using profiles is to create one, optionally giving it a meaningful `name` that is unique within your organization.

```
import Kernel, { ConflictError } from '@onkernel/sdk';

const kernel = new Kernel();

try {
  await kernel.profiles.create({ name: 'profiles-demo' });
} catch (err) {
  if (err instanceof ConflictError) {
    // Profile already exists
  } else {
    throw err;
  }
}
```

## [](#2-start-a-browser-session-using-the-profile-and-save-changes)2. Start a browser session using the profile and save changes

After creating the profile, reference it by its `name` or `id` when creating a browser. Set `save_changes` to true to persist any state created during this session back into the profile when the browser is closed.

```
const kernelBrowser = await kernel.browsers.create({
  profile: {
    name: 'profiles-demo',
    save_changes: true,
  },
});
```

## [](#3-use-the-browser-then-close-it-to-persist-the-state)3. Use the browser, then close it to persist the state

After using a browser with `save_changes: true`, closing the browser will save cookies and local storage into the profile.

Calling `browser.close()` does **not** save the profile state. You **must** explicitly delete the Kernel browser (or let the browser [timeout](https://www.kernel.sh/docs/browsers/termination#automatic-deletion-via-timeout)) to persist the Profile.

```
console.log('Live view:', kernelBrowser.browser_live_view_url);

// Navigate and create login state...

await kernel.browsers.deleteByID(kernelBrowser.session_id);
```

## [](#4-start-a-new-session-with-the-saved-profile-read-only)4. Start a new session with the saved profile (read-only)

Create another browser using the same profile name. Omitting `save_changes` leaves the stored profile untouched.

```
const kernelBrowser2 = await kernel.browsers.create({
  profile: { name: 'profiles-demo' },
});

console.log('Live view:', kernelBrowser2.browser_live_view_url);
```

## [](#loading-a-profile-into-an-existing-browser)Loading a profile into an existing browser

You can load a profile into a browser after it has been created using the [update browser endpoint](https://www.kernel.sh/docs/api-reference/browsers/update-browser-session).

```
// Create a browser without a profile
const kernelBrowser = await kernel.browsers.create();

// Later, load a profile into the browser
await kernel.browsers.update(kernelBrowser.session_id, {
  profile: { name: 'profiles-demo' }
});
```

You cannot load a profile into a browser that was already created with a profile. The browser must have been created without any profile configuration.

## [](#other-ways-to-use-profiles)Other ways to use profiles

The API and SDKs support listing, deleting, and downloading profile data as JSON. See the [API reference](https://www.kernel.sh/docs/api-reference/profiles/list-profiles) for more details.

## [](#notes)Notes

* A profile’s `name` must be unique within your organization.
* Profiles store cookies and local storage. Start the session with `save_changes: true` to write changes back when the browser is closed.
* To keep a profile immutable for a run, omit `save_changes` (default) when creating the browser.
* Multiple browsers in parallel can use the same profile, but only one browser should write (`save_changes: true`) to it at a time. Parallel browsers with `save_changes: true` may cause profile corruption and unpredictable behavior.
* Profile data is encrypted end to end using a per-organization key.

----
url: https://www.kernel.sh/docs/reference/mcp-server
----

Our Model Context Protocol (MCP) server lets any compatible AI model or agent launch Chromium browsers, execute Playwright code, capture video replays, and automate web interactions from Kernel’s cloud platform via a single secure endpoint.

## Setup Instructions

### General (Transports)

Use the streamable HTTP endpoint where supported for increased reliability. If your client does not support remote MCP, use `mcp-remote` over stdio. Kernel’s server is a centrally hosted, authenticated remote MCP using OAuth 2.1 with dynamic client registration.

## Authentication

### OAuth (Recommended)

The MCP server uses OAuth 2.1 for user authentication. When you connect through supported clients, you’ll be prompted to authorize access via your browser.

### API Key Authentication

For programmatic access or service-to-service authentication, you can use your Kernel API key instead of OAuth. Add you

##About Kernel

Kernel is a browser infrastructure platform that provides cloud browsers for AI agents and web automations. It enables fast spin-up (under 30ms) with GPU acceleration when needed, reusable sessions, and autoscaling browsers to scale workloads. The official documentation covers 165 pages of technical reference. This entry reflects the current stable release.

category:[Other]

source: https://kernel.sh/docs