Debug a Kernel Browser Session

Diagnose a misbehaving Kernel cloud browser session using the Kernel CLI. The CLI has full access to the session's VM — status, screenshots, Playwright execution, log files, and in-VM command execution — which is everything you need to localize a failure to bot detection, a Chrome crash, a network/DNS problem, or live-view/WebRTC issues.

Inputs

Two things drive the investigation:

1. Session ID — the browser session to debug (e.g. abc123example456xyz).
2. Issue description — what's going wrong (e.g. "ERR_HTTP2_PROTOCOL_ERROR navigating to a specific site", "browser not responding", "page not loading", "live view is blank").

If either is missing, ask for it before proceeding. The issue description determines which checks below to weight.

Prerequisites

Load the kernel-cli skill for Kernel CLI installation and authentication. Its references cover the full command surface (browser-management, filesystem-ops, process-execution, computer-controls) when you need options beyond the ones below.

Core CLI commands