Kernelhub vs Silicon Audit

KernelHub connects the CLI coding agents already running on your own machine — Claude Code, Codex, Antigravity CLI — to the phone in your pocket. Getting started is one command. In your project folder, run icloser pair. It prints a code. Scan it. That's the setup. WHAT IT IS FOR You leave your desk mid-task. Later, on your phone, you want to know what your agent decided, approve the thing it's waiting on, or say one more sentence — without re-explaining the whole project from scratch. KernelHub keeps tasks, agents, memory and files together, so the next device picks up where the last one stopped. HOW IT WORKS • Say it in plain language. Your sentence is queued verbatim and handed to the CLI runtime on your own machine. • Watch it happen. A single timeline shows what needs you, what is running, and what finished. • Decide from anywhere. Approvals, questions and conflicts are actionable from the phone. • Seven permission levels — read, change code, run commands, search the web, push, system ops, delete or migrate data — each confirmed per device. Permission granted on one device is never inherited by another. WHAT IT DOES NOT DO KernelHub never holds your model API keys, and the backend never calls a model. Every conclusion comes from the runtime signed in on your own machine. The workspace token lives in this device's Keychain and never syncs via iCloud. When it cannot read your workspace, it says so. It will not draw an empty screen and let you conclude there is nothing to do — that misreading is exactly what this app exists to prevent. REQUIREMENTS A machine running icloser, reachable from your phone, with at least one CLI coding agent installed and signed in.

Silicon Audit shows what your Apple device's chip and kernel report about their security features: in plain language first, and in full technical detail when you want it. WHAT IT CHECKS • Memory tagging hardware (MTE) and Apple's Memory Integrity Enforcement • Pointer authentication and branch target protection • Speculation hardening and constant-time execution • The kernel protections Apple documents for your chip family • On macOS, whether memory tagging is active right now, and whether it is active for this app Every answer says where it came from. Measured means your device's kernel reported it through the public sysctl interface. Documented means Apple published it, and the source and date are shown. The app never guesses: a chip Apple has not documented reads as not documented. LOOK DEEPER Every check opens to the facts behind it, and every fact to its raw reading: the sysctl key, type, length and value. All readings sit on three shelves: security protections, chip and instruction sets, device and system. A measurement screen explains how the report was produced. CHANGE MONITORING The first reading becomes a baseline. Silicon Audit checks again when you open it and periodically in the background, and tells you if anything moved: a protection that was reported on and now reports off, a value that changed, a key that appeared or vanished, a system update. Each change is explained at three depths: a plain sentence, what it could mean, and the technical before and after. Notifications are optional. The monitor sees only what the kernel exposes, and the app says so. EXPORT AND CONTRIBUTE Export a JSON report with provenance on every fact. It contains no serial number, device identifier, hostname or account. Contribute it to the public results database on GitHub to help map which Apple chips report which protections. PRIVACY No network access. No analytics. Readings stay on your device unless you share them. Open source under Apache-2.0. Apple Watch: measure on the watch itself and send the report to your iPhone. Apple TV: export as a QR code.