Index / PicoClaw · updated Oct 2, 2026
PicoClaw
sipeed/picoclaw · healthy · rank 9 of 43 by stars
An ultra-lightweight Go rewrite of the personal AI assistant concept, built from scratch by Sipeed to run on $10 hardware with under 10MB of RAM. It trades ecosystem breadth for extreme portability across x86, ARM, RISC-V, MIPS, and LoongArch.
Facts
Repository
Runtime
Posture
Community
Security breakdown
Composite 72 / 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 · 91 files examined
6 providers · gateway support
Pinned models
glm-4.7 released 2025-12-22 — 9 months old (from the public model catalogue)
Pin last edited 3 months ago
Evidence
Decision
Why choose PicoClaw over OpenClaw?
Why choose this
- Runs in under 10MB RAM versus OpenClaw's much heavier footprint
- Millisecond boot time on $10 hardware
- Single Go binary deployable across many CPU architectures
Tradeoffs
- Smaller community and fewer ready-made skills and integrations
- Less mature sandboxing and multi-tenant isolation
- Younger project with pre-1.0 stability expectations
Best fit
- Running an AI assistant on cheap SBCs and embedded boards
- Users who want minimal RAM and instant startup
- Self-hosters comfortable configuring Go binaries
Avoid if
- You need a large plugin/skills ecosystem out of the box
- You want a polished GUI or managed cloud experience
- You require mature multi-user sandboxing
Strong evidence from README, commits, and release data confirms the lightweight Go architecture and active maintenance. Sentiment and security posture are inferred from limited third-party discussion, so those scores carry moderate uncertainty.
AI layer reviewed Sep 21, 2026 · how this is written
Star activity
30,027 stars today
Overview
PicoClaw is an independent open-source AI assistant written entirely in Go by Sipeed, inspired by NanoBot but rebuilt from scratch through a self-bootstrapping process where the agent itself drove architecture migration. Its headline claim is extreme efficiency: it runs on $10 hardware with under 10MB of RAM and millisecond boot times, targeting x86_64, ARM64, MIPS, RISC-V, and LoongArch — roughly 99% less memory than OpenClaw.
Architecturally it is a single static Go binary with a provider abstraction layer supporting multiple LLM backends, configurable model fallback chains, and a tool system with per-agent allowlists. Recent commits show active hardening: govulncheck-driven dependency updates, fixes to Anthropic tool_use serialization for reloaded history, and guardrails that steer the write_file tool away from destructive overwrites toward append/edit alternatives.
Compared to OpenClaw, PicoClaw deliberately sacrifices ecosystem breadth and rich UI for portability and cost. It is best understood as the edge/embedded branch of the Claw family — ideal for SBCs, routers, and always-on low-power deployments, but with a smaller community, fewer integrations, and pre-1.0 maturity.