Index / PicoClaw · updated Sep 3, 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 boards with ~10MB RAM. Massive community traction and rapid commit velocity make it the flagship 'tiny claw' for edge and embedded deployments.
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 2 months ago
Evidence
Decision
Why choose PicoClaw over OpenClaw?
Why choose this
- Runs on ~10MB RAM and $10 hardware, far below OpenClaw's footprint
- Millisecond boot times from a single static Go binary
- Broad architecture support: x86_64, ARM64, MIPS, RISC-V, LoongArch
Tradeoffs
- Smaller skill/plugin ecosystem than OpenClaw
- Fewer built-in guardrails and sandboxing features
- Younger project with less battle-tested tooling
Best fit
- Running an AI assistant on cheap SBCs and embedded boards
- Resource-constrained edge or offline deployments
- Users who want a minimal Go binary instead of a heavy runtime
Avoid if
- You need a mature plugin/skill ecosystem
- You require strong built-in sandboxing for untrusted tool execution
- You want multi-user or multi-tenant operation out of the box
Strong evidence from the README, active commit history, and release data supports the performance and positioning claims. Security posture and ecosystem maturity are less certain due to limited third-party audits and mostly promotional community discussion.
AI layer reviewed Aug 24, 2026 · how this is written
Star activity
29,935 stars today
Overview
PicoClaw is an independent open-source personal AI assistant written entirely in Go by Sipeed, inspired by NanoBot but rebuilt from scratch through a 'self-bootstrapping' process where the AI agent itself drove the architecture migration. Its headline claim is extreme efficiency: it runs on $10 hardware with under 10MB of RAM and millisecond boot times, roughly 99% less memory than OpenClaw, and ships as a single static binary supporting x86_64, ARM64, MIPS, RISC-V, and LoongArch.
Architecturally, PicoClaw focuses on a minimal core with configurable model providers, fallback chains, and a tool system (write_file, edit_file, append_file) with per-agent allowlists and enable flags. Recent commits show active hardening: fixes to Anthropic provider tool_use serialization, safer file-overwrite guidance that respects available tools, and govulncheck-driven dependency updates. This indicates a maturing codebase with real attention to correctness and security hygiene.
Compared to OpenClaw, PicoClaw trades ecosystem breadth and built-in guardrails for deployability-anywhere minimalism. It is the natural choice for embedded boards, offline edge nodes, and users who want a tiny Go binary rather than a heavy runtime, but users needing rich skills, sandboxing, or multi-tenant operation will find OpenClaw (or containerized alternatives) stronger.