Skip to main content
Integrations · Kernel
A Guild agent controls Kernel cloud browsers to automate web tasks without exposing credentials to agent code. Guild injects your Kernel API key server-side through its credential proxy. Credential policies let you restrict which browser operations each agent or workspace can call.

Book a demo

See how teams govern agents that use Kernel.

Talk to sales

Get access to Guild, then connect Kernel to your first agent.

What the Kernel integration exposes

The tools cover browser session lifecycle: create, update, and delete sessions, and acquire or release browsers from pools. Agents can execute Playwright code or run JavaScript in a persistent Node.js runtime, perform low-level computer actions such as clicking, typing, scrolling, and dragging, and manage reusable profiles that persist state across sessions. Recording and replay tools let agents start and stop session recordings and list saved replays.

How it works

1

Open Credentials in Guild

Go to Access & setup > Credentials in your Guild account or organization. This page lists connected credentials and shows a gallery of available integrations.
2

Connect your Kernel key

Click Connect, select kernel, and paste your API key into the API Key field. Guild sends the key as a bearer token in the Authorization header on every request.
3

Scope the credential

Choose account-wide, one workspace, a single member, or a dedicated agent scope. See Credentials for details on each scope and how Guild resolves which credential to use.

Why Kernel access needs governing

Kernel tools can create and delete browser sessions, execute arbitrary Playwright code, and read clipboard contents. Without rules, any agent using the credential can run any of these operations. Credential policies let you write ALLOW and DENY rules that Guild’s credential proxy enforces before a request leaves Guild. You can restrict specific operations by name or glob pattern, scope rules to individual agents or workspaces, and limit HTTP methods to block mutating calls. Guild stores the Kernel API key server-side and injects it after the policy check passes. Agent code never sees the key. You can scope a credential to one workspace, one member, or a single agent so that sessions created by an automation pipeline stay separate from those used in development. Guild’s credential proxy enforces every policy check; agents cannot bypass it.

About the Kernel integration

Agents can create and manage cloud browser sessions, including browser pools and reusable profiles that persist state across sessions. They can execute Playwright scripts, run JavaScript in a persistent runtime, and perform low-level computer actions such as clicking, typing, scrolling, and dragging. Agents can also record and replay browser sessions for auditing or debugging. The integration is guildai~kernel.

Authentication

  • Type: API key
  • Header: Guild sends the key as a bearer token in the Authorization header

Setup

1

Connect Kernel

In Guild, go to Access & setup > Credentials, click Connect, select kernel, and paste the key into API Key.
See Credentials for workspace, member, and agent-scoped credentials.

Usage

Selecting specific tools

Tools are named with the kernel_ prefix. Use pick() to include only what your agent needs.

Tools

Tools in the latest published version of guildai~kernel:

Frequently asked questions

No. The Kernel catalog entry lists no webhook events, so the integration has no event-based triggers. Agents must poll session state using the available session tools.
Write a credential policy with a DENY rule for the delete operations and scope it to the agent you want to restrict. Guild’s credential proxy enforces the rule before any request reaches Kernel. See Credential policies.
Go to Access & setup > Credentials, click Connect, select kernel, and paste your key. You can scope it to the whole account, one workspace, yourself, or a single agent.
Yes. Tools use the kernel_ prefix. Use pick() from the Guild Agent SDK to include only the tools your agent needs, as shown in the tool sets docs.

Put a governed agent on Kernel cloud browsers today

Book a demo

See how teams govern agents that use Kernel.

Talk to sales

Get access to Guild, then connect Kernel to your first agent.
Also runs on Guild: Browserbase · Cloudflare · Firecrawl · Pinecone Read: Docs: Credential policies · Credentials · Tools in agents
Last modified on November 20, 2026