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 accesslocalhost 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
Thekernel browsers ssh command requires websocat to be installed locally:
- macOS
- Linux
Basic usage
Open an interactive SSH shell to a browser VM: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:
localhost:8080 and reach your local development server.
Setup only
Configure SSH on the VM without opening a connection:Flags
| Flag | Description |
|---|---|
-i, --identity <path> | Path to SSH private key (generates ephemeral if not provided). |
-L, --local-forward <spec> | Local port forwarding (localport:host:remoteport). |
-R, --remote-forward <spec> | Remote port forwarding (remoteport:host:localport). |
--setup-only | Setup SSH on VM without connecting. |

