Index / Picobot · updated Oct 24, 2026
Picobot
louisho5/picobot · healthy · rank 31 of 50 by stars
A single-binary Go rewrite of the OpenClaw concept that runs on a $5 VPS with ~10MB RAM and instant cold starts. It trades ecosystem breadth for extreme minimalism: persistent memory, tool calling, and Telegram/Discord/Slack/WhatsApp channels in a ~9MB binary.
Facts
Repository
Runtime
Posture
Community
Security breakdown
Composite 68 / 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 · 27 files examined
1 provider · gateway support
Pinned models
gemini-2.5-flash released 2025-06-17 — 17 months old (from the public model catalogue)
Pin last edited 8 months ago
Evidence
Decision
Why choose Picobot over OpenClaw?
Why choose this
- ~9MB single binary vs heavyweight runtime stack
- Millisecond cold starts and ~10MB idle RAM
- Zero dependencies; runs on Termux, Pi, or $5 VPS
Tradeoffs
- Far smaller skills and plugin ecosystem
- No control UI dashboard or canvas features
- Fewer supported chat channels and integrations
Best fit
- Self-hosters on cheap VPS or Raspberry Pi hardware
- Users wanting a personal chat agent without Python/Node bloat
- Operators who value fast cold starts and tiny containers
Avoid if
- You need a large skills/plugin ecosystem
- You want a mature control UI or dashboard
- You require strong sandboxing for untrusted tool execution
Evidence is solid for architecture and footprint (detailed README, active commits, recent v0.3.0 release), but community sentiment is uncertain due to zero Reddit matches and only indirect web mentions.
AI layer reviewed Oct 5, 2026 · how this is written
Star activity
1,343 stars today
Overview
Picobot is a minimalist, Go-based reimplementation of the OpenClaw personal AI agent concept, packaged as a single ~9MB static binary with zero runtime dependencies. It delivers the core agent loop — persistent memory, tool calling, skills, and multi-channel messaging (Telegram, Discord, Slack, WhatsApp) — while idling at roughly 10MB of RAM and booting in milliseconds, making it viable on a $5 VPS, Raspberry Pi, or even an Android phone via Termux.
Configuration is handled through environment variables and a simple onboard CLI flow, with all state persisted to a single data directory that maps cleanly into Docker volumes. Recent development shows active maintenance: a configurable exec-command denylist for safer shell tool use, a configurable agent timeout (raised from a hardcoded 60s to 300s) applied consistently across CLI and gateway channels, improved Slack socket-mode error logging, and growing test coverage.
Compared to OpenClaw, Picobot deliberately sacrifices breadth — no control UI, no canvas, a much smaller skills ecosystem, and fewer integrations — in exchange for operational simplicity and an extremely small resource footprint. It is best understood as the 'runs anywhere' end of the OpenClaw-alternative spectrum: ideal for solo self-hosters who want a private, always-on chat agent without managing Python environments or heavyweight containers.