A single Rust binary that runs your AI agent on your hardware, not theirs
ZeroClaw is an autonomous agent runtime you host yourself, with pluggable LLMs, 30+ channels, and enough security knobs to make a paranoid sysadmin nod approvingly.

What it does ZeroClaw is a single Rust binary that becomes your personal AI assistant infrastructure. You configure it via one TOML file, point it at an LLM provider (Anthropic, OpenAI, Ollama, or ~20 others), and it listens and responds across whatever channels you enable — Discord, Telegram, Matrix, email, voice, webhooks, CLI, even GPIO pins on a Raspberry Pi. It can run supervised (you approve risky actions), unsupervised, or in “YOLO mode” for dev boxes where you trust the machine.
The interesting bit The security model is unusually thorough for an open-source agent project: OS-level sandboxes (Landlock, Bubblewrap, Seatbelt, Docker), workspace boundaries, command policies, and cryptographic tool receipts on every action. Most agent frameworks assume cloud hosting; ZeroClaw assumes you own the machine and want to keep it that way. The SOP engine for event-triggered procedures with approval gates is also a nice touch — it turns the agent from a chatbot into something closer to an autonomous operator that still knows when to raise its hand.
Key highlights
- Single binary, ~6.6 MB minimal build, installable via curl or source with feature flags
- 30+ channel adapters (Discord, Telegram, Matrix, email, voice, webhooks, ACP for IDE integration)
- Pluggable providers with fallback chains when one flakes
- Hardware support: GPIO / I2C / SPI / USB on embedded boards via a
Peripheraltrait - Web dashboard for chat, memory browsing, config editing, cron management
- systemd / launchctl / Windows Service integration for always-on operation
- Dual MIT/Apache-2.0 license, Rust 2024 edition
Caveats
- The README mentions “~20” LLM providers and “30+” channels but doesn’t list them exhaustively; you’ll need to check the docs or source for what’s actually implemented
- Configuration uses a specific V3 TOML schema with four required section types; the README warns that misplacing an
api_keyvs. using stored auth profiles breaks OpenAI Codex integration - Hardware support is trait-based but the actual breadth of tested boards is unclear from the README alone
Verdict Self-hosters, homelab operators, and developers who want an agent that runs on their Pi or laptop without phoning home to a SaaS platform should look here. If you want a managed cloud assistant with zero configuration, this is the wrong direction — that’s the point.