sorajez/zeroclaw

https://github.com/morpheum-labs/mormclaw https://github.com/zeroclaw-labs/zeroclaw https://github.com/morpheum-labs/mormclaw

🦀 ZeroClaw — Personal AI Assistant

Zero overhead. Zero compromise. 100% Rust. 100% Agnostic.
⚡️ Runs on $10 hardware with <5MB RAM: That's 99% less memory than OpenClaw and 98% cheaper than a Mac mini!

https://github.com/zeroclaw-labs/zeroclaw/graphs/contributors

Built by students and members of the Harvard, MIT, and Sundai.Club communities.

🌐 Languages: 🇺🇸 English · 🇨🇳 简体中文 · 🇯🇵 日本語 · 🇰🇷 한국어 · 🇻🇳 Tiếng Việt · 🇵🇭 Tagalog · 🇪🇸 Español · 🇧🇷 Português · 🇮🇹 Italiano · 🇩🇪 Deutsch · 🇫🇷 Français · 🇸🇦 العربية · 🇮🇳 हिन्दी · 🇷🇺 Русский · 🇧🇩 বাংলা · 🇮🇱 עברית · 🇵🇱 Polski · 🇨🇿 Čeština · 🇳🇱 Nederlands · 🇹🇷 Türkçe · 🇺🇦 Українська · 🇮🇩 Bahasa Indonesia · 🇹🇭 ไทย · 🇵🇰 اردو · 🇷🇴 Română · 🇸🇪 Svenska · 🇬🇷 Ελληνικά · 🇭🇺 Magyar · 🇫🇮 Suomi · 🇩🇰 Dansk · 🇳🇴 Norsk

ZeroClaw is a personal AI assistant you run on your own devices. It answers you on the channels you already use (***, ***, Slack, ***, Signal, iMessage, Matrix, IRC, Email, Bluesky, Nostr, Mattermost, Nextcloud Talk, DingTalk, Lark, QQ, Reddit, LinkedIn, ***, MQTT, WeChat Work, and more). It has a web dashboard for real-time control and can connect to hardware peripherals (ESP32, STM32, Arduino, Raspberry Pi). The Gateway is just the control plane — the product is the assistant.

If you want a personal, single-user assistant that feels local, fast, and always-on, this is it.

Website · Docs · Architecture · Getting Started · Migrating from OpenClaw · Troubleshoot · ***

Preferred setup: run zeroclaw onboard in your terminal. ZeroClaw Onboard guides you step by step through setting up the gateway, workspace, channels, and provider. It is the recommended setup path and works on macOS, Linux, and Windows (via WSL2). New install? Start here: Getting started

Subscription Auth (OAuth)

• OpenAI Codex (*** subscription)
• Gemini (Google OAuth)
• Anthropic (API key or auth token)

Model note: while many providers/models are supported, for the best experience use the strongest latest-generation model available to you. See Onboarding.

Models config + CLI: Providers reference Auth profile rotation (OAuth vs API keys) + failover: Model failover

Install (recommended)

Runtime: Rust stable toolchain. Single binary, no runtime dependencies.

Homebrew (macOS/Linuxbrew)

bash
brew install zeroclaw

One-click bootstrap

bash
git clone https://github.com/zeroclaw-labs/zeroclaw.git
cd zeroclaw
./install.sh

zeroclaw onboard runs automatically after install to configure your workspace and provider.

Quick start (TL;DR)

Full beginner guide (auth, pairing, channels): Getting started

bash
# Install + onboard
./install.sh --api-key "sk-..." --provider openrouter

# Start the gateway (webhook server + web dashboard)
zeroclaw gateway                # default: 127.0.0.1:42617
zeroclaw gateway --port 0       # random port (security hardened)

# Talk to the assistant
zeroclaw agent -m "Hello, ZeroClaw!"

# Interactive mode
zeroclaw agent

# Start full autonomous runtime (gateway + channels + cron + hands)
zeroclaw daemon

# Check status
zeroclaw status

# Run diagnostics
zeroclaw doctor

Upgrading? Run zeroclaw doctor after updating.

From source (development)

bash
git clone https://github.com/zeroclaw-labs/zeroclaw.git
cd zeroclaw

cargo build --release --locked
cargo install --path . --force --locked

zeroclaw onboard

Dev fallback (no global install): prefix commands with cargo run --release -- (example: cargo run --release -- status).

Migrating from OpenClaw

ZeroClaw can import your OpenClaw workspace, memory, and configuration:

bash
# Preview what will be migrated (safe, read-only)
zeroclaw migrate openclaw --dry-run

# Run the migration
zeroclaw migrate openclaw

This migrates your memory entries, workspace files, and configuration from ~/.openclaw/ to ~/.zeroclaw/. Config is converted from JSON to TOML automatically.

Security defaults (DM access)

ZeroClaw connects to real messaging surfaces. Treat inbound DMs as untrusted input.

Full security guide: SECURITY.md

Default behavior on all channels:

• DM pairing (default): unknown senders receive a short pairing code and the bot does not process their message.
• Approve with: zeroclaw pairing approve <channel> <code> (then the sender is added to a local allowlist).
• Public inbound DMs require an explicit opt-in in config.toml.
• Run zeroclaw doctor to surface risky or misconfigured DM policies.

Autonomy levels:

Sandboxing layers: workspace isolation, path traversal blocking, command allowlisting, forbidden paths (/etc, /root, ~/.ssh), rate limiting (max actions/hour, cost/day caps).

📢 Announcements

Use this board for important notices (breaking changes, security advisories, maintenance windows, and release blockers).

Highlights

• Lean Runtime by Default — common CLI and status workflows run in a few-megabyte memory envelope on release builds.
• Cost-Efficient Deployment — designed for $10 boards and small cloud instances, no heavyweight runtime dependencies.
• Fast Cold Starts — single-binary Rust runtime keeps command and daemon startup near-instant.
• Portable Architecture — one binary across ARM, x86, and RISC-V with swappable providers/channels/tools.
• Local-first Gateway — single control plane for sessions, channels, tools, cron, SOPs, and events.
• Multi-channel inbox — ***, ***, Slack, ***, Signal, iMessage, Matrix, IRC, Email, Bluesky, Nostr, Mattermost, Nextcloud Talk, DingTalk, Lark, QQ, Reddit, LinkedIn, ***, MQTT, WeChat Work, WebSocket, and more.
• Multi-agent orchestration (Hands) — autonomous agent swarms that run on schedule and grow smarter over time.
• Standard Operating Procedures (SOPs) — event-driven workflow automation with MQTT, webhook, cron, and peripheral triggers.
• Web Dashboard — React 19 + Vite web UI with real-time chat, memory browser, config editor, cron manager, and tool inspector.
• Hardware peripherals — ESP32, STM32 Nucleo, Arduino, Raspberry Pi GPIO via the Peripheral trait.
• First-class tools — shell, file I/O, browser, git, web fetch/search, MCP, Jira, Notion, Google Workspace, and 70+ more.
• Lifecycle hooks — intercept and modify LLM calls, tool executions, and messages at every stage.
• Skills platform — bundled, community, and workspace skills with security auditing.
• Tunnel support — Cloudflare, Tailscale, , Open, and custom tunnels for remote access.

Why teams pick ZeroClaw

• Lean by default: small Rust binary, fast startup, low memory footprint.
• Secure by design: pairing, strict sandboxing, explicit allowlists, workspace scoping.
• Fully swappable: core systems are traits (providers, channels, tools, memory, tunnels).
• No lock-in: OpenAI-compatible provider support + pluggable custom endpoints.

Benchmark Snapshot (ZeroClaw vs OpenClaw, Reproducible)

Local machine quick benchmark (macOS arm64, Feb 2026) normalized for 0.8GHz edge hardware.

Notes: ZeroClaw results are measured on release builds using /usr/bin/time -l. OpenClaw requires Node.js runtime (typically ~390MB additional memory overhead), while NanoBot requires Python runtime. PicoClaw and ZeroClaw are static binaries. The RAM figures above are runtime memory; build-time compilation requirements are higher.