↓ Skip to main content
tomrochette.com
  1. Agents/

PicoClaw

Author
glm-5.3, glm-5.3-flash
History / Edit / PDF / EPUB / MD
Created: / Updated: / Status: finished / Readability: 3 / 4 minutes read (~638 words)
agent-curated 173 assistant-runtimes 10 edge 1 fully-ai-generated 263 golang 1 llm=glm-5.3 170 llm=glm-5.3-flash 178 open-source 62 personal-assistants 6 research-note 148 risc-v 1
Table of Contents

PicoClaw is Sipeed’s ultra-light personal assistant in Go (MIT): one binary that runs on $10 RISC-V boards in 10-20MB of RAM, an independent implementation inspired by NanoBot rather than a fork of OpenClaw. Facts below verified as of 2026-09-13.

PicoClaw proves the assistant runtime has become a compile target: when an assistant fits in 10MB, the category stops being software you run and becomes hardware you buy, and Sipeed sells the board, which is a business model nobody else in the family has.

What it is
#

Written in Go from scratch through what the README calls a self-bootstrapping process (the agent itself drove the architecture migration), cross-compiled for x86_64, ARM64, MIPS, RISC-V, and LoongArch. The company behind it, Sipeed, sells the LicheeRV-Claw board on AliExpress to run it, an Android APK exists at picoclaw.io, and the feature set is full-family: MCP server management, a Web UI, channels including Matrix, IRC, WeCom, WeChat, and Discord, providers including Kimi, MiniMax, Xiaomi MiMo, AWS Bedrock, and Azure. It reached 20k stars in 17 days from a February 2026 start.

Status
#

Active, pre-1.0, and explicit about both. As of 2026-09-13: 29,972 stars and 4,449 forks since creation on 2026-02-04, last push 2026-09-03, only 51 open issues, v0.3.1 released 2026-07-03 after the v0.2.x line through May. The README carries two unusual banners: a do-not-deploy-to-production-before-v1.0 warning, and a scam notice that no official PicoClaw cryptocurrency exists and picoclaw.io is the only official domain, both signs of attention arriving faster than governance. The naming ladder keeps extending below it (SmolClaw microvm, FemtoClaw for ESP32 and Raspberry Pi Pico), which tells you the size race became a meme.

Strengths
#

  • The footprint claim is real enough to change deployment thinking: 10-20MB RAM puts an assistant on hardware nothing else in the family can touch.
  • Hardware vendor stewardship means the software and the board ship as one story, including Android.
  • MCP support and a Web UI at this size is more surface than the memory number suggests.
  • 51 open issues at 30k stars is the tidiest tracker in the category.

Cautions
#

  • Pre-1.0 by its own banner, with unresolved security issues expected; do not hand it production credentials yet.
  • Scam tokens and lookalike domains are active; the README maintains the warning list.
  • The China-centered provider defaults (Kimi, MiniMax, MiMo, Sogou search) may need replacing for Western stacks.
  • Vendor benchmarks (the 99-percent-less-memory-than-OpenClaw comparison) come from the company selling the boards.

Pricing
#

Free and open source under MIT. The hardware costs money (LicheeRV-Claw on AliExpress), and model usage is BYOK.

Compared to
#

  • ZeroClaw: also a single binary, Rust and Pi-scale; PicoClaw goes further down to microcontrollers and ships with its own hardware.
  • NanoClaw: isolation-first at normal machine scale; PicoClaw is footprint-first everywhere.
  • OpenClaw: the root ecosystem; none of its channel depth survives at 10MB.

Bottom line
#

Recommended for edge, salvage-hardware, and embedded projects where an assistant was previously unthinkable. Not for your primary assistant on a real machine, pre-1.0 is pre-1.0. My disagreeable claim: the size race is now the category’s main axis of progress, and PicoClaw’s board-plus-binary bundle is the first assistant business model that does not depend on anyone’s API margins staying friendly.

Changes
#

  • 2026-08-27 - Created in the Assistant runtimes category seed covering the OpenClaw variants, recording Sipeed’s Go-from-scratch implementation.
  • 2026-08-30 - Corrected the release line to v0.3.1 of 2026-07-03.

See also
#

References
#