Batch Computer Actions
Execute 1-100 computer actions sequentially in a Kernel browser, stopping on the first error. Actions can click, type, press keys, and submit forms or cause other irreversible external effects.
Kernel provides cloud browsers, computer controls, Playwright execution, session replays, and persistent browser profiles for building browser-based agents and automations.
Execute 1-100 computer actions sequentially in a Kernel browser, stopping on the first error. Actions can click, type, press keys, and submit forms or cause other irreversible external effects.
Send a read-only GET, HEAD, or OPTIONS request through a Kernel browser's network stack, inheriting its cookies, TLS fingerprint, proxy settings, and default headers. For POST, PUT, PATCH, or DELETE, use Browser HTTP Request.
Send a state-changing POST, PUT, PATCH, or DELETE request through a Kernel browser's network stack, inheriting its cookies, TLS fingerprint, proxy settings, and default headers. The target may change external systems irreversibly. For GET, HEAD, or OPTIONS, use Browser Curl.
Click at browser viewport coordinates with an optional mouse button, click phase, modifiers, and repetition count. A click can submit forms, place orders, or cause other irreversible external effects.
Create a Kernel browser session; defaults to a headless browser with a 60-second inactivity timeout.
Create an empty persistent browser profile, optionally with a unique name, for reuse by later browser sessions.
Permanently end and delete a Kernel browser session by ID or name.
Stop and permanently delete a named, non-default Playwright executor from a Kernel browser. Its running call fails, its name can be reused, and close_tab controls whether its tab is also closed. To restart the reserved default executor, use Restart Default Playwright Executor.
Permanently delete a browser profile by ID or name.
Download a profile's stored browser state. Current profiles return the requested tar.zst or uncompressed tar format; legacy profiles may return JSON regardless of the requested format. The profile must have captured state from a browser session.
Drag a mouse button through an ordered path of browser viewport coordinates, with optional timing, linear-step, and modifier controls. A drag can move items, submit controls, or cause other irreversible external effects.
Execute arbitrary TypeScript or JavaScript with Playwright access to the browser; the code may navigate, mutate pages, submit forms, or cause irreversible external effects.
Get safe operational details for one browser session by ID or name, optionally including a deleted session.
Get the current mouse cursor coordinates in a Kernel browser session.
Get one browser profile by its ID or exact name.
Download a completed browser replay as MP4. If the replay is still processing, the action asks the caller to retry later.
List browser sessions, optionally filtered by lifecycle state, search text, tags, or region, one offset page at a time.
List the default and named Playwright executors for a Kernel browser, including whether each is busy and its owned tab when available.
List browser profiles, optionally filtered by substring or exact name, one offset page at a time.
List replay recordings for a headful browser session without returning signed viewer URLs.
Move the cursor to browser viewport coordinates, optionally using a timed human-like path and held modifier keys.
Press an ordered sequence of X11 keys or key chords in a browser, optionally holding modifiers or holding the sequence for a duration. Key presses may submit forms, activate controls, or trigger other irreversible external effects.
Read the current text from a Kernel browser session's clipboard.
Rename a Kernel browser profile by ID or exact name. Rename profiles only when they are not in use because sessions referencing the old name may fail to save their changes.
Restart a Kernel browser's reserved default Playwright executor. Its process is stopped and any running call fails irreversibly; queued and later calls run on the new process. This does not delete a named executor or close a tab.
Save a running browser's current state to exactly one destination profile ID or name, creating a named profile when needed and overwriting an existing destination. This restarts the browser, closes all active connections, reloads pages, and loses in-memory page state; reconnect after completion. It does not attach the profile or enable save_changes.
Scroll horizontally or vertically at browser viewport coordinates, optionally while holding modifier keys.
Hide or show the cursor in a Kernel browser session.
Start recording a headful Kernel browser session and return its replay identifier and recording metadata without exposing its signed viewer URL.
Stop an active replay recording for a Kernel browser identified by ID or name.
Capture the full browser viewport or a rectangular region as a PNG download.
Type text into the currently focused browser element with an optional per-keystroke delay.
Update mutable settings on an existing Kernel browser session.
Upload and activate one or more unpacked Chromium extension ZIP archives in an existing running browser. This ad-hoc operation does not add extensions to Kernel's reusable extension catalog. Chromium may restart, disrupting active browser connections.
Write text to the system clipboard of a Kernel browser session.
The Kernel integration connects your Dench AI CRM directly to Kernel, so agents can read and act on your Kernel data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
35 actions are available for agents to invoke on your behalf. Every call runs through Kernel's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Kernel and click Connect — you'll authorize access through Kernel's own sign-in flow. No API keys or code required.
Ask an agent to use Kernel in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Kernel integration connects your AI CRM to Kernel, so AI agents can work with your Kernel data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Kernel integration currently exposes 35 actions, including Batch Computer Actions, Browser Curl, Browser HTTP Request, Click, Create Browser, and Create Profile. Agents invoke them on your behalf from chat or from automations.
No. You connect Kernel from your Dench workspace using Kernel's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Kernel's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Kernel connection from your workspace settings at any time.