Browser-Harness with Kernel Cloud Browsers

This skill documents how to drive a Kernel cloud browser with browser-harness (browser-use's open-source CDP harness). browser-harness already supports any CDP endpoint via the BU_CDP_WS env var — the work this skill covers is extracting that URL from the Kernel CLI, picking the right kernel browsers create flags, and using the Kernel session ID as the harness daemon name so sessions don't collide.

When to Use This Skill

Use this skill when you need to:

• Drive a Kernel browser from browser-harness instead of the user's local Chrome
• Extract a CDP URL from kernel browsers create -o json to feed into BU_CDP_WS
• Span multiple harness calls across a long task (mint, drive, inspect, drive more, tear down)
• Run parallel harness sessions against multiple Kernel browsers without socket collisions

Prerequisites

• Load the kernel-cli skill for Kernel CLI installation and authentication.
• If browser-harness is not already on $PATH, install it per its setup-prompt. If it is already installed, do not reinstall or run setup prompts — go straight to minting the Kernel browser.
• Install jq only if missing (used to pull fields from the CLI's -o json output).