Index / PicoClaw · updated Aug 17, 2026
PicoClaw
sipeed/picoclaw · healthy · rank 9 of 43 by stars
A from-scratch Go rewrite of the personal AI assistant concept, boasting <10MB RAM footprint on $10 hardware. Recently shipped v0.3.1 with active AI-assisted development and multi-arch edge focus.
Facts
Repository
Runtime
Posture
Community
Security breakdown
Composite 75 / 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 · 90 files examined
6 providers · gateway support
Pinned models
glm-4.7 released 2025-12-22 — 8 months old (from the public model catalogue)
Pin last edited 2 months ago
Evidence
Decision
Why choose PicoClaw over OpenClaw?
Why choose this
- Runs on $10 hardware with <10MB RAM (99% less than OpenClaw)
- Multi-arch support including RISC-V, MIPS, LoongArch
- Single Go binary, no runtime dependencies, instant boot
Tradeoffs
- Smaller plugin/extension ecosystem compared to OpenClaw
- Less mature cross-platform UI (Canvas, mobile) than OpenClaw
- Fewer pre-built integrations and community channels
Best fit
- Edge and IoT deployments on cheap hardware
- Hobbyists wanting a tiny local AI assistant
- Multi-arch experimentation (RISC-V, MIPS)
Avoid if
- Users needing heavy enterprise sandboxing
- Those requiring rich plugin ecosystem like OpenClaw
- Teams wanting guaranteed commercial support
Evidence from README, recent commits, and web mentions shows active development and clear positioning; uncertainty remains on real-world security hardening and multi-user scaling.
AI layer reviewed Aug 2, 2026 · how this is written
Star activity
29,861 stars today
Overview
PicoClaw is an ultra-lightweight personal AI assistant written from scratch in Go by Sipeed, explicitly inspired by NanoBot and positioned as a lean alternative to OpenClaw. It targets edge and embedded hardware, running on as little as $10 devices with under 10MB RAM while supporting diverse architectures including x86_64, ARM64, MIPS, RISC-V, and LoongArch.
The project was uniquely 'self-bootstrapped'—the AI agent itself drove the architecture migration and code optimization—and continues to evolve with AI-assisted commits (e.g., Claude co-authored fixes for tool safety and provider compatibility). Recent work focuses on hardening tool access (write_file overwrite guards) and robust provider history handling (anthropic tool_use fallback), indicating a security-conscious development pace.
Unlike OpenClaw's broader ecosystem with rich Canvas UI and mobile presence, PicoClaw prioritizes minimal footprint and deployability, making it ideal for constrained environments. The v0.3.1 release and active community show a healthy, emerging project with MIT licensing and a clear edge-first vision.