Skip to main content
SSH into a running Kernel browser VM for debugging, running commands, or setting up port forwarding.

Forward local dev server to browser

A common use case is exposing a local development server to the remote Kernel browser. This lets the browser access localhost URLs that point to your local machine:
Kernel detects browser activity via WebRTC (live view) or CDP connections. SSH connections alone don’t count as activity, so without --timeout, your browser may be cleaned up while you’re connected via SSH. Either set a timeout or keep the live view open.

Prerequisites

The kernel browsers ssh command requires websocat to be installed locally:

Basic usage

Open an interactive SSH shell to a browser VM:
By default, this generates an ephemeral ed25519 SSH keypair for the session. The keypair is automatically cleaned up when the session ends.

Using an existing SSH key

Specify an existing SSH private key instead of generating an ephemeral one:
The corresponding .pub file must exist alongside the private key (e.g., ~/.ssh/id_ed25519.pub).

Port forwarding

Port forwarding uses standard SSH syntax.

Local forwarding (-L)

Forward a local port to a port on the VM. Useful for accessing services running inside the VM from your local machine:

Remote forwarding (-R)

Forward a VM port to a port on your local machine. Useful for exposing a local development server to the browser:
This allows code running in the browser to access localhost:8080 and reach your local development server.

Setup only

Configure SSH on the VM without opening a connection:
This installs and configures the SSH server on the VM, then prints the manual connection command. Useful if you want to connect with your own SSH client or configuration.

Flags