- SPECIMEN
ZeroClaw
- FILED AS
Rust multi-agent runtime with a dated changelog feed on Releasebot
- INTAKE DATE
- 2026-09-08
- CLASS
- AI Platform
- METHOD
- 1 page scraped, 3 search passes, 24 community sources
Koda Score = weighted blend: capability 35, ease 20, value 25, momentum 20.
Capability reflects an ambitious feature set we have not audited; ease is dragged down by consistent setup complaints and the desktop app only just returning; value is decent given a free tier and open releases but the $29 Pro tier is thinly described; momentum is high with three point releases in roughly ten weeks and contributor counts climbing from 56 to 73.
8 MIN READTwo subsystems most agent runtimes still only sketch, a supervised Standard Operating Procedure engine and a sandboxed WebAssembly plugin host, landed in a single release alongside a security wave that closed multiple SSRF gaps and fixed path traversal; that is the case for watching ZeroClaw closely. The case against bumping it unattended is the same changelog: 379 commits in v0.8.3, 454 in v0.8.5, and a Reddit thread describing two days of broken installs. Run it in a supervised sandbox with the feed piped into your upgrades channel, and treat every minor version as a review item rather than a routine dependency bump.
ZeroClaw's v0.8.3 and v0.8.5 alone carried 833 commits, and Releasebot did not surface the first of them until seven weeks after it shipped.
Captured: releasebot.io/updates/zeroclaw on 2026-09-08.
The short version.
4 LINESSubscribe to the Releasebot ZeroClaw feed via RSS, Slack, n8n, MCP, or API and route it into the channel where your team approves upgrades.
Do not rely on Releasebot alone: it first saw v0.8.3 on Sep 3, 2026 for a Jul 15 release, and GitHub already lists v0.8.5.
The v0.8.3 release added a fail-closed SOP engine, a wasmtime plugin host, and a GitHub/Gitea forge channel; read those notes before upgrading anything that runs unattended.
Community setup reports are rough enough that a two-day install is a documented outcome, so budget for it.
What it actually does.
8 CAPABILITIES- Standard Operating Procedure engine
- A daemon tick drives live procedures with typed step contracts, cron and calendar triggers, and an approval plane that fails closed on timeout.
- WebAssembly plugin host
- A wasmtime component-model host runs tool, channel, and memory plugins with per-call execution limits, a config jail, and signature policy checks at load.
- Git forge channel
- GitHub and Gitea/Forgejo providers plus a unified git_forge tool let the agent live where code reviews happen, with SOP ingress.
- A2A agent discovery
- Since v0.8.2 agents can describe and discover one another over the gateway, the first agent-to-agent interop path.
- Desktop app via Tauri sidecar
- The kernel ships as a Tauri sidecar, bringing back a self-contained desktop app built around Quickstart for people who do not live in a terminal.
- Cost and usage ledger
- Task-attributed usage accounting with an offline pricing catalog and by-period, org-billed views.
- Security hardening wave
- v0.8.3 closed multiple SSRF gaps, added constant-time token comparison, fixed path traversal, and cleared several RUSTSEC advisories.
- Releasebot feed outputs
- The changelog is available as RSS, email, CLI, MCP, API, Slack, and n8n, so it can land directly in an upgrade-approval workflow.
How you would actually use it.
3 PLAYS- The upgrade gate
- Follow ZeroClaw on Releasebot, push the Slack or n8n output into the channel where version bumps get approved, and add the GitHub Releases page as a second source to cover the feed's lag.WHOPlatform engineer owning agent infrastructurePAYOFFBreaking changes like the v0.8.3 rewrite of procedures and plugins show up as a dated diff before anyone bumps a version in an unattended workflow.
- Agent in the review queue
- Use the Git forge channel to bind the agent to the repo, route tool approvals to a distinct approver channel, and wire SOP ingress so procedures can start from forge events.WHOTeam lead on GitHub or a self-hosted Gitea/ForgejoPAYOFFAutomation that participates in code review without giving it unsupervised authority.
- Supervised procedures instead of fire and forget
- Encode the runbook as an SOP with cron or calendar triggers, rely on the approval plane failing closed on timeout, and keep driverless steps blocked by the capability registry.WHOOps owner automating recurring runbooksPAYOFFProcedures you can supervise, resume, and audit, with a task-attributed usage ledger showing what each one cost.
Pricing, straight.
3 TIERS- Verdict on the price
- The free tier plus public GitHub releases make it cheap to evaluate, but no pricing page was scraped and the Pro tier is described only as advanced features, so confirm what $29 actually buys before committing.
What people online are saying.
5 QUOTEDNobody is talking about the changelog feed itself yet; the ZeroClaw chatter splits between excitement over a tiny, fast Rust runtime and frustration over installs and documentation.
ZeroClaw has incredible potential, but in its current state it is a poorly documented, frustrating mess; two days went into broken installs.
CritiqueSeems insanely fast; why buy a Mac Mini when you can run ZeroClaw on $10 hardware?
PraiseStill intended for enthusiasts willing to overcome difficulties.
CritiqueI was running a small MCP server and got tired of Python deps, Docker, and config files that outlive their purpose.
MixedThe honest part.
5 LIMITATIONSThe Releasebot feed lags: v0.8.3 was dated Jul 15, 2026 but first seen Sep 3, and GitHub already lists v0.8.5.
Setup is repeatedly called complex and poorly documented, with one Reddit user reporting two days of broken installs.
Only 7 release notes are in the feed, curated from 10 sources, so history before the v0.8 rewrite is thin.
Pricing tiers are described generically and no pricing page was found; Enterprise is contact-only.
We have not audited the runtime itself; feature claims come from the vendor's release notes.
The field.
2 ALTERNATIVES- OpenClaw
- The larger, better-known agent runtime that ZeroClaw is repeatedly positioned against as the heavier incumbent.PICK IT WHENYou want the bigger ecosystem and more people who have already hit your problem, and you can accept a heavier footprint.
- GitHub Releases for zeroclaw-labs/zeroclaw
- The upstream release page, already showing v0.8.5 while Releasebot tops out at v0.8.3.PICK IT WHENYou need the freshest notes on the day they ship rather than a curated multi-source summary.
Getting started.
3 STEPSSign up on Releasebot and Follow ZeroClaw at releasebot.io/updates/zeroclaw.
Pick an output that lands where upgrades get decided: Slack, n8n, RSS, email, MCP, or API.
Add the GitHub Releases page as a second source and read the full diff of each new version before touching an unattended workflow.
Quick answers.
4 ANSWERS- Is the Releasebot feed current enough to gate upgrades on?
- Not on its own. Releasebot first saw the Jul 15 v0.8.3 release on Sep 3, 2026, and GitHub Releases already lists v0.8.5 with 454 commits from 73 contributors. Use the feed for the curated summary and the GitHub page for freshness.
- Is ZeroClaw free?
- Structured site data shows a Free tier at $0, a Pro tier at $29 per month, and a contact-only Enterprise tier. No dedicated pricing page was scraped, and the tier descriptions are generic, so verify before budgeting.
- How does ZeroClaw relate to OpenClaw?
- Community posts consistently frame ZeroClaw as the smaller, faster Rust alternative and OpenClaw as the heavier incumbent, including a r/agi thread contrasting a 34MB ZeroClaw with OpenClaw's size. Both have Releasebot feeds you can follow side by side.
- How painful is the install?
- Rough, by the community's account. The site data lists complex setup as a limitation, a Reddit post describes two days of broken installs and poor documentation, and a Russian-language review calls it a tool for enthusiasts willing to overcome difficulties. v0.8.2 added automatic PATH setup and v0.8.3 brought back a Quickstart desktop app, so it is improving.
The bottom line.
SPECIMEN 0216 CLOSEDFollow the feed today, and pair it with GitHub Releases because Releasebot is currently two versions behind. Adopt the runtime itself only where a human approves each upgrade.
Field research: 1 page scraped · 3 search passes · 24 community sources. Reviewed by the Koda desk on 2026-09-08.