zeroclaw
ZeroClaw is a local-first, single-binary Rust personal AI assistant you run on your own devices. It provides a gateway/control plane with a web dashboard to manage an always-on assistant that can connect to multiple chat/communication channels (e.g., WhatsApp/Telegram/Slack/Discord/Signal/Email/Matrix/IRC/etc.), integrate with hardware peripherals (e.g., ESP32/STM32/Arduino/Raspberry Pi GPIO), and run autonomous/"hands" workflows, SOPs, and tools (including mentions of MCP and many integrations).
Score Breakdown
⚙ Agent Friendliness
🔒 Security
README highlights several security features: DM pairing/allowlist by default for unknown senders, explicit opt-in for public inbound DMs, autonomy levels with approval gating, sandboxing layers (path traversal blocking, command allowlisting, forbidden paths like /etc,/root,~/.ssh), and rate limiting/cost caps. However, the excerpt does not provide detailed guidance on TLS configuration requirements, token storage/redaction practices, precise scope granularity, or dependency vulnerability management.
⚡ Reliability
Best When
You want an on-device, always-on personal assistant that can manage many communication channels and tools under configurable autonomy and sandbox policies.
Avoid When
You need a simple, documented public API surface for programmatic third-party clients, or you cannot control/monitor local security settings for DM pairing/allowlisting and tool access.
Use Cases
- • Personal AI assistant that lives on your own hardware and stays online
- • Multi-channel personal inbox/assistant for DMs and inbound messages
- • Local autonomous workflows/SOPs with approvals and sandbox/policy controls
- • Managing agent actions and memory via a local web dashboard
- • Connecting external devices/peripherals to agent workflows
- • Integrating with common LLM providers via OAuth/API-key auth profiles with model/provider failover
Not For
- • Untrusted multi-user deployments without strong isolation and DM policy controls
- • Use as a hosted SaaS where uptime/SLA is required
- • Scenarios requiring a standardized public REST/GraphQL API contract for third-party developers
- • Environments where you cannot safely operate an always-on process that can access messaging channels and tool execution
Interface
Authentication
Auth model includes subscription-based OAuth for some providers and API key/token auth for others; documentation suggests provider/profile rotation and failover, but the README excerpt does not specify fine-grained OAuth scopes or how tokens are scoped/rotated internally.
Pricing
Pricing for ZeroClaw itself is not described in the provided README excerpt; it likely depends on your selected LLM/provider usage and any third-party channel integrations.
Agent Metadata
Known Gotchas
- ⚠ ZeroClaw is an always-on, multi-channel agent; inbound DMs should be treated as untrusted and require pairing/allowlisting per the documented default DM policy.
- ⚠ Autonomy levels (ReadOnly/Supervised/Full) and sandbox/policy controls are critical; agents should respect and not bypass these controls.
- ⚠ The README excerpt mentions many tools and MCP, but the provided content does not expose a clear, machine-consumable MCP tool schema or public agent SDK contract.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for zeroclaw.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-29.