Pairing a device

Pairing joins a screen to a workspace. The workspace UUID is the address; the token is the credential.

From the desktop

Open KernelHub Desktop on the machine running the executor and choose Pair this phone. A code appears. Scan it with the phone.

From a link

If the camera is not an option, the same pairing is available as a join link. Opening it on the phone joins the same workspace.

Where the token lives

The token is carried in the URL fragment, not the query string. Fragments are not sent to the server, so the credential does not end up in access logs or in a Referer header. Once the app has stored it, it is removed from the address bar.

Changing networks

In this release the phone does not connect to your computer directly: the phone and the Executor each connect to the hosted gateway (kernelhub.icloser.xyz), and pairing records the workspace on that gateway, not an address on your local network. So the two devices do not need to be on the same network, and switching Wi-Fi or moving the phone to cellular does not require scanning again — each side just needs internet access. On iOS the app may ask once whether it may access your local network; in this release the phone talks to the hosted gateway, so either answer leaves pairing and tasks unaffected.

When scanning does nothing

• The phone cannot reach the gateway. After scanning, the phone claims the workspace at kernelhub.icloser.xyz: it needs internet access, and its network must not block that host. Whether it shares a network with the computer does not matter.
• The agent is not running. The client shows whether a machine is picking work up. If nothing is, start icloser run again.

Multiple workspaces

One machine can hold several workspaces, one per directory. A device paired to one workspace sees only that workspace — permissions and tasks never cross between them.