Index / MicroClaw · updated Oct 24, 2026
MicroClaw
microclaw/microclaw · healthy · rank 34 of 50 by stars
A self-hosted Rust agent platform inspired by nanoclaw, shipping one embeddable agent core across a server, a native GPUI desktop app, and an SDK. It emphasizes durable sessions, persistent memory, and governed tool access with recent security-hardening commits.
Facts
Repository
Runtime
Posture
Community
Security breakdown
Composite 78 / 100 · how these are scored
higher is safer
higher is safer
higher is safer
higher is safer
higher is riskier
Model access
Read from the repository, not written by a model · 34 files examined
2 providers · custom endpoint
Pinned models
claude-sonnet-4-5-20250929 released 2025-09-29 — 13 months old (dated in the model id)
Pin last edited 20 days ago
Evidence
Decision
Why choose MicroClaw over OpenClaw?
Why choose this
- Rust core with very low resource footprint
- Embeddable SDK for embedding the agent engine in Rust apps
- Native GPUI desktop app with checkpoints and approvals
Tradeoffs
- Far smaller community and channel coverage
- No Reddit presence and thin third-party discussion
- Younger project with breaking changes on main
Best fit
- Rust developers wanting an embeddable agent engine
- Self-hosters needing always-on chat agents with scheduling
- Users wanting a native desktop agent app with approvals
Avoid if
- You need a large plugin/skill ecosystem
- You want a managed hosted tier
- You need proven production stability (main branch moves fast)
Evidence from the README and recent commits is solid for architecture and security posture, but community sentiment is uncertain due to zero Reddit matches and web results mostly referencing OpenClaw rather than MicroClaw itself.
AI layer reviewed Oct 5, 2026 · how this is written
Star activity
748 stars today
Overview
MicroClaw is a self-hosted agentic AI platform written in Rust, inspired by nanoclaw. It is built around a single embeddable Agent Engine exposed through three surfaces: MicroClaw Server for always-on chat channels, Web/API access, scheduling, and automation; MicroClaw Work, a native GPUI desktop app for local workspace-centered agent sessions with approvals and checkpoints; and microclaw-sdk, which lets other Rust applications embed the same engine, tools, policy, memory, skills, and runtime events.
The architecture targets work that outlasts a single request: multi-step tool use, resumable sessions, durable delivery, persistent memory, scheduled tasks, and governed extensions all share one runtime. Recent commits show active security hardening, including a GovernanceGuard that blocks file-tool writes to governance files (AGENTS.md, SOUL.md, config, path allowlists) with symlink-aware path resolution, plus memory deduplication fixes and Telegram partial-quote context forwarding.
Compared to OpenClaw, MicroClaw trades ecosystem breadth for a lean Rust core, an embeddable SDK, and a native desktop experience. It is MIT licensed, actively maintained (v0.7.0, frequent commits, Dependabot automation), and recommends the stable branch for production since main moves quickly. Its community footprint is still small, with minimal Reddit or third-party discussion.