PicoClaw

PicoClaw is an ultra-lightweight, self-hosted AI assistant written in Go, designed for low-cost hardware, that supports multiple LLM providers, chat channels,…

  • AI
PicoClaw is an ultra-lightweight, self-hosted AI assistant written in Go, designed for low-cost hardware, that supports multiple LLM providers, chat channels, MCP integration, multimodal file handling, and a browser-based web interface for configuration.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

78/100 Good

Maintained
87last commit 94 days ago
Popular
9030,111 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
801 GB minimum RAM, runs on ARM
Security check
88no serious findings, 2 minor, CI, tests

Availability: platform listings confirmed today, links checked 15 days ago

GitHub stars
30,111
Open issues
36
Last commit
2026-08-19
Latest release
v0.3.1
License
MIT
Activity
stale

Checked 13 days ago - source: GitHub (sipeed/picoclaw)

Resources & Compatibility

Minimum requirements: 1 GB RAM. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Do the first run, then add API keys Clone the repo, run the launcher once to create docker/data/config.json, add your API keys there, then start it and open http://localhost:18800. Without the first run and API keys, PicoClaw may stop early or fail to reach AI models. source
  • Copy the security example file Copy the example security configuration file to ~/.picoclaw/.security.yml before starting PicoClaw. This creates the security settings file the app expects, avoiding missing-config surprises. source
  • Keep your main settings file Your API keys and model choices live in docker/data/config.json, so keep a backup or know where that folder is. If that file is lost or overwritten, you may have to re-enter your API keys and app settings. source
  • First-run setup After first run, define a password, add your LLM provider API key, optionally configure a chat channel such as Telegram, then start the gateway. source

Fetched 39 days ago - each note links to its source

Alternatives (5)

  • AgentGPT - AgentGPT allows you to configure and deploy Autonomous AI agents.
  • Manus - Transforms thoughts into actions with personalized travel itineraries, stock analysis, and educational content while autonomously completin…
  • OpenClaw - OpenClaw is an open-source, self-hosted AI assistant gateway that connects large language models (LLMs) to Discord, Telegram, and WhatsApp,…
  • OpenHands - OpenHands is an open-source AI software development agent that writes, reviews, and tests code.
  • ZeroClaw - claw done right 🦀.

Checked 39 days ago - source: AlternativeTo

Common questions

Why might PicoClaw stop early or fail to reach AI models after installation?

Run the launcher once to create docker/data/config.json, add your API keys there, then start PicoClaw. Without that first run and valid API keys, it may stop early or fail to reach AI models.

Where should I back up my PicoClaw settings?

Your API keys and model choices live in docker/data/config.json, so keep a backup of that file or folder. If it is lost or overwritten, you may have to re-enter your API keys and app settings.

How do I avoid missing security configuration when starting PicoClaw?

Copy the example security configuration file to ~/.picoclaw/.security.yml before starting PicoClaw. This creates the security settings file the app expects.

How can I make the PicoClaw gateway reachable beyond localhost?

Set PICOCLAW_GATEWAY_HOST=0.0.0.0 in your environment or config. If using the Web Launcher, run the launcher with the -public flag.

Answers sourced from docs.picoclaw.io, github.com, github.com

Community

Collected 49 days ago - public community threads