Null docs
The cookbook.
Task-oriented and honest: real commands, verified versions, no seasoning you don't need. Machine-readable too — llms.txt, llms-full.txt, and a .md twin for every page.
Start
- What is the Null ecosystem A family of single-binary Zig tools for running AI agents on your own hardware.
- Choose your setup Decide between a single agent, the managed stack, or the minimal sibling.
- Install NullHub Get the control plane running via Docker, a release binary, or from source.
- Run your first agent Install NullClaw through NullHub, start it, and send it a message.
- Install NullClaw directly The fastest path — Homebrew, Docker, Nix, or build from source. No hub required.
Recipes
- Personal assistant One NullClaw, your chat apps, local memory. The simplest complete setup.
- Shared knowledge Give agents a common, permission-aware memory with NullPantry.
- Durable backlog A task rail agents claim from, report to, and never lose — NullTickets plus NullClaw.
- Multi-agent workflow Graph workflows across a worker fleet — NullBoiler over NullTickets and NullClaw.
- Observable agent stack Traces, evals and cost per run — NullClaw into NullWatch, rendered by NullHub.
Operate
- Updates and rollback Keep components current with NullHub, and recover when an update misbehaves.
- Backup and restore Every component stores state in local files. Know where, copy them, sleep well.
- Secrets and networking Default ports, loopback-first binding, tokens, CORS and tunnels across the stack.
- Security Sandboxing, pairing, encrypted secrets and the trust model across the family.
- Troubleshooting The diagnostic tour — health checks, logs, and the failures people actually hit.
Reference
- CLI reference Every documented command across the family, one component per table.
- Configuration and environment Config file locations, formats, and environment variables for every component.
- APIs and OpenAPI HTTP surfaces, self-describing schemas, and agent protocols across the stack.
- Compatibility matrix Versions, licenses, platforms, install paths and hub-manageability, per component.