Support

KernelHub v1.0.2 · Last updated 21 August 2026

Most questions are answered faster by a guide than by an email, so those come first.

Contact

Email support@icloser.xyz. We answer in English and Chinese.

Before you write

Three things make almost any report answerable. Without them, the first reply can only be a request for them.

1. Version and build

   Run icloser version; on the phone or desktop it is on the About screen. “Latest” is not a version — two builds of 1.0.2 can behave differently.

2. The task id

   Every task has one, shown on its card. With it we can point at the timeline and the diff instead of guessing at a description.

3. What you expected, and what happened

   Separately. “It didn't work” collapses those into one and loses the part that matters.

Requesting access

KernelHub is invitation-only while v1.0.2 rolls out. Downloads are open to everyone — you can install the CLI, start the executor and pair your phone before you have a code. Activating your account is what needs one.

Email support@icloser.xyz with the machine you plan to run it on and what you want to build. One code activates your account for 30 days — the activation lives on your account, not on a workspace, so a second project or a second machine does not need another code.

Already have a code? How to activate, and what happens when it expires.

Things that are usually not bugs

• A task stops and asks for a permission. That is the design — it stops before doing the work, so nothing is half-done while it waits.
• A runtime is marked NOT_READY, or a task says it cannot hold the delete boundary. Also the design — and it is bookkeeping, not a block: when nothing proves a tier is also held by something else, we say so rather than pretend, and writes, edits and execs still go through the Tool Server against your grants. The delete/migrate boundary stops and asks you to release that one run.
• Nothing happens after you send a task. Check the executor is still running on the machine that holds the code.

Uninstalling

Remove the icloser binary from ~/.local/bin and delete ~/.kernelhub (local configuration and the task ledger), ~/.kernelhub-gate (identity credentials) and ~/.kernelhub-protected (the protected root, if present). If you made it resident, run icloser daemon uninstall first. On Windows it depends on how you installed: the one-line PowerShell command puts it in %LOCALAPPDATA%\Programs\icloser — delete that folder and take it out of your user PATH; the offline bundle carries scripts\uninstall.ps1; the MSI is removed from Settings > Apps. Nothing else is left on the machine.

Legal

See the Privacy Policy and the Terms of Service.