nullclaw/nullhub

NullHub – a local management hub for the NullClaw AI‑agent ecosystem

What it is

• A single‑binary application written in Zig that bundles a Svelte web UI. It acts as a control plane for a family of AI‑agent components (NullClaw, NullBoiler, NullTickets, NullWatch).
• Think of it as a lightweight, self‑hosted “Docker‑Compose‑like” manager, but specialised for the NullClaw ecosystem. It can install, start, stop, monitor, and update each component, and it exposes a REST/CLI API for automation.

Key capabilities

Feature	What you get
Install wizard	Guided, manifest‑driven setup that knows the dependencies between components (e.g., linking NullTickets to NullBoiler).
Process supervision	Starts components, restarts them on crash with exponential back‑off, and tracks their health via HTTP checks.
Health dashboard	Real‑time status cards and log streaming (SSE) for every instance.
Cross‑component linking	Auto‑creates configuration so that NullTickets talks to NullBoiler, NullWatch can visualise runs, etc.
Config editor	Structured UI for each component’s JSON config plus a raw‑JSON fallback.
One‑click updates	Downloads new releases, migrates configs, and can roll back on failure.
Multi‑instance support	Run several independent copies of the same component side‑by‑side.
CLI + Web UI	Human‑friendly browser UI and a full‑featured command‑line interface for scripts.
Mission Control	A local “agent mission replay” sandbox: deterministic replay of a failure‑recovery scenario, checkpoint forking, and telemetry visualisation without any external model APIs.

How you use it

# Build the binary (needs Zig and npm for the UI)
zig build
# Run it – it starts the server and opens the UI in your browser
./zig-out/bin/nullhub

The UI is served at http://nullhub.localhost:19800 (or 127.0.0.1). From there you can install any of the Null* components, start them, view logs, and explore the Mission Control replay screen.

Architecture at a glance

• Backend (Zig) – HTTP server, process supervisor, installer, and a manifest engine that reads nullhub-manifest.json files shipped by each component.
• Frontend (SvelteKit) – Compiled to static assets and embedded into the binary via Zig’s @embedFile. UI modules are loaded on demand.
• State storage – All configuration, binaries, logs, and replay artifacts live under ~/.nullhub/.
• Proxies – NullHub forwards API calls to the actual component services (NullBoiler, NullTickets, NullWatch) so the UI talks to a single origin.

Who might find it useful?

• Developers building or testing AI‑agent pipelines with NullClaw who want a local, reproducible environment.
• Researchers experimenting with workflow orchestration (NullBoiler) and trace analysis (NullWatch) without relying on cloud services.
• Teams that need a simple way to spin up multiple isolated instances for CI or demos.

What you need to run it

• Zig 0.16 (compiler) and npm (to build the Svelte UI). The binary can auto‑install missing system tools via common package managers.
• Basic Unix tools (curl, tar). On Windows it will try to use winget/choco.

Development & testing

• Unit and integration tests are run with zig build test ….
• UI development: cd ui && npm run dev.
• End‑to‑end scripts under tests/ verify the full install‑run‑monitor cycle.

---

NullHub is not a machine‑learning model itself; it is the orchestration and observability layer for the NullClaw suite of AI‑agent tools.