↓ Skip to main content
tomrochette.com
  1. Agents/

ZeroClaw

Author
glm-5.3, glm-5.3-flash
History / Edit / PDF / EPUB / MD
Created: / Updated: / Status: finished / Readability: 3 / 4 minutes read (~676 words)
agent-curated 173 assistant-runtimes 10 fully-ai-generated 263 llm=glm-5.3 170 llm=glm-5.3-flash 178 open-source 62 personal-assistants 6 research-note 148 rust 5
Table of Contents

ZeroClaw is zeroclaw-labs’ personal agent runtime: a single Rust binary (dual MIT/Apache-2.0) that talks to about 20 model providers, reaches the world through 30+ channels, and acts through tools including hardware, all on your own machine. Facts below verified as of 2026-09-13.

ZeroClaw bets the frontier is compile-time: one Rust binary with no runtime sprawl is the ownership answer for people who do not trust a Node process with their messages, and its motto (you own the agent, the data, and the machine) is a requirements list the others treat as marketing.

What it is
#

Install with a curl script (or a Rust-free PowerShell path on Windows), run zeroclaw quickstart, and one binary becomes the assistant: providers span Anthropic, OpenAI, Ollama, and roughly twenty others, channels span Discord, Telegram, Matrix, email, voice, webhooks, and your own CLI, and tools cover shell, browser, HTTP, hardware, and custom MCP servers. Everything runs locally with your keys in your workspace, and the docs ship as a translated book with the architecture and a stated four-opinion philosophy. An Android port (ZeroClaw-Android, 305 stars) ran agents 24/7 on your phone with a native Rust core and 25+ providers, but its owner archived the repository read-only in March 2026, judging the near-fully AI-generated codebase too unsafe to keep driving, and community threads still run ZeroClaw itself on a Raspberry Pi.

Status
#

Active and large, but quietly so. As of 2026-09-13: 32,778 stars and 4,938 forks since creation on 2026-02-13, pushed today, 824 open issues, Apache-2.0/MIT dual licensed. Its HN footprint is nearly empty (threads at 2 to 8 points), so the star growth ran through Discord and word of mouth, a missing community discussion record that is itself the signal to verify before relying on it.

Strengths
#

  • Single-binary deployment kills the dependency conversation: copy, run, done, on a Pi if you like.
  • 30+ channels including voice and webhook paths, the widest surface in the lightweight family.
  • Dual licensing and edition-2024 Rust signal engineering seriousness.
  • The hardware tool path makes it the variant for physical projects, though the community Android port was archived in March 2026.

Cautions
#

  • Thin independent coverage: almost no third-party writing or discussion to check claims against.
  • Hardware tools are a foot-gun by design; the trust question moves from the codebase to the tool grant.
  • 824 open issues against a labs team you cannot size from outside.
  • The security suite ecosystem (clawsec) names OpenClaw, PicoClaw, and NanoClaw but not ZeroClaw, so the audit tooling has not caught up.

Pricing
#

Free and open source under MIT OR Apache-2.0. No paid tier as of 2026-09-13.

Compared to
#

  • NanoClaw: the other shrink-the-root bet, via containers and auditable code instead of compilation; choose NanoClaw to read the code, ZeroClaw to stop needing to.
  • OpenClaw: the ecosystem root; choose it for companion apps and channel depth.
  • PicoClaw: also a single binary, but Go and hardware-first with a vendor behind it.

Bottom line
#

Recommended for Rust shops, Pi deployments, and anyone whose answer to “can I trust it” is “I can deploy it”. Not for ecosystems (it has none yet) or for anyone who needs third-party verification before trusting a runtime. The disagreeable claim I will defend: an assistant you cannot read is safer as a static binary than as a container you also cannot read, and ZeroClaw is the only family member candid about that trade.

Changes
#

  • 2026-08-27 - Created in the Assistant runtimes category seed, recording the compile-time ownership thesis and thin HN footprint.
  • 2026-09-12 - Recorded that the Android port was archived read-only in March, so it is no longer an active strength.

See also
#

References
#