KernelHub Platforms
Where the Executor and the console run, and where the phone clients stand today.
KernelHub is two halves. The half that does the work runs on your own machine. The half you drive it from is a phone or a browser.
The machine that holds your code
node -v and npm -v both print a version. Runtimes are installed through npm, and the KernelHub installer does not install Node for you. Step by step: Windows from zero · Mac from zero · Linux from zeromacOS
Apple Silicon and Intel. Install with the one-line command from the download page; it puts icloser in ~/.local/bin and does not ask for sudo. The local console is installed alongside it.
Linux
x86-64 and arm64, same one-line command, same install location.
Windows
x86-64 and ARM64, installed with the PowerShell line from the download page. The package includes the Executor, the local console and a standalone uninstaller, published with SHA-256 sums like every other artifact.
One thing to know before you start: in this release the phone does not connect to this machine directly — the phone and the Executor each connect to the hosted gateway, so nothing has to find anything on the local network. If a phone scanned successfully but nothing moves, run icloser doctor on this machine first to see whether the gateway is reachable and the Executor is running, rather than suspecting the pairing itself.
Verifying what you downloaded
Every binary is published with its SHA-256 on the download page, and the install script refuses to install a file whose checksum does not match the release manifest. If checksum verification is impossible on the machine, it refuses rather than proceeding — installing and then mentioning that nothing was verified is the same as not verifying.
The screens you drive it from
The state below is read from the release manifest that ships with this build, not written into this page by hand.
The browser
The local console runs on the machine itself, in any current browser, at 127.0.0.1:18092. See Local Console.