nullclaw drops tiny Zig agent runtime

nullclaw matters because it attacks the assumption that agent infrastructure has to be bloated to be useful. If it can keep adding integrations without losing its tiny footprint, it could become a serious base layer for local-first AI automation.

• –The repo positions nullclaw as a zero-runtime-dependency agent system with multi-provider LLM support, hybrid SQLite plus vector memory, and broad channel coverage from CLI to Telegram, Discord, Slack, and WhatsApp
• –Release v2026.3.5 is more about hardening than flashy launch theater, with fixes for malformed tool-call markup, Windows-safe bootstrap handling, provider error surfacing, reasoning parsing, and Telegram draft streaming
• –The Zig implementation is the real differentiator: a static binary, low memory use, and cheap-board compatibility make it unusually plausible for SBCs, homelabs, and embedded-ish deployments
• –nullclaw also lowers migration friction by keeping OpenClaw-compatible config and shipping an explicit migration path from OpenClaw memory and settings
• –Third-party coverage is already framing it as a lightweight OpenClaw alternative, which suggests the market for smaller, self-hosted agent runtimes is real and growing