Local Console
A management console for the machine that holds your code. It runs on that machine, listens only on localhost, and shows you the same state the phone sees.
The console is a separate program from the Executor. Installing KernelHub puts both on the machine: icloser (the Executor, which does the work) and kernelhub-desktop (the console, which shows you what is going on). Starting one does not start the other.
Opening it
Prints what state this machine is in, where the console is listening, and what to do next. It does not need a workspace — it answers on a fresh install, which is exactly when you most need it to.
Opens the console in your default browser. Over SSH or in any other non-interactive shell it prints the address instead of trying to open a window.
Where it listens
Port 18092, bound to 127.0.0.1. That bind address is the point: the console can read workspace tokens and grant permissions, so it is reachable only from the machine it runs on. It is not exposed to your network, and there is no setting that exposes it.
To drive that machine from somewhere else, pair a phone. That path is authenticated and goes through the gateway; the console is not a remote admin panel.
What is on it
- Workspace — which workspace this machine is bound to, and switching between them.
- Runtime — which CLI coding agents are installed here and which permission tiers each can actually hold.
- Permissions — what this device is allowed to do.
- Approvals — anything waiting for you to say yes or no.
- Tasks — what has run, with the Live Diff and the result for each.
- Environment — the developer toolchain on this machine, from a real probe.
- AI Employees — registered roles and whether their environment is ready.
Language
English, 简体中文 and 繁體中文. A fresh install opens in English and does not guess from your browser; your choice is remembered on this machine.