---

PicoClaw is an independent open-source project initiated by Sipeed, written entirely in Go from scratch — not a fork of OpenClaw, NanoBot, or any other project.

🌱 Active Fork

This repository is an actively maintained fork of PicoClaw. Development continues here, with ongoing fixes, dependency updates, and new features.

PicoClaw is an ultra-lightweight personal AI assistant inspired by NanoBot. It was rebuilt from the ground up in Go through a "self-bootstrapping" process — the AI Agent itself drove the architecture migration and code optimization.

Runs on $10 hardware with 10–20 MB RAM in recent builds.

[!CAUTION]
Security Notice

• NO CRYPTO: PicoClaw has not issued any official tokens or cryptocurrency. All claims on pump.fun or other trading platforms are scams.
• OFFICIAL DOMAIN: The ONLY official website is picoclaw.io, and company website is sipeed.com
• BEWARE: Many .ai/.org/.com/.net/... domains have been registered by third parties. Do not trust them.
• NOTE: PicoClaw is in early rapid development. There may be unresolved security issues. Do not deploy to production before v1.0.
• NOTE: PicoClaw has recently merged many PRs. Recent builds may use 10–20 MB RAM. Resource optimization is planned after feature stabilization.

📢 News

2026-09-29 🚀 v0.4.0 Released! This substantial release adds MCP CLI management and Web UI configuration, native Anthropic Messages API support, configurable web search (including Keenable and Kagi), configurable logging and virtual models, cross-platform serial-tool support, enhanced hooks and isolation, plus numerous channel, provider, security, and build fixes.

2026-09-28 🌱 Project revived! Development has resumed and will continue to be actively maintained in this fork.

Earlier news...

2026-05-11 🛒 LicheeRV-Claw on AliExpress! You can now purchase LicheeRV-Claw from AliExpress, making it easier to try PicoClaw on compact RISC-V hardware.

2026-05-28 🚀 v0.2.9 Released! MCP server management in Web UI, configurable Sogou-backed web search, tool feedback animation in channels, pretty_print and disable_escape_html defaults, and numerous bug fixes across providers and channels.

2026-05-14 🚀 v0.2.8 Released! MCP CLI commands (show, add, list, remove, test, edit), empty object instead of null for MCP tool parameters, and build fixes.

2026-05-07 🚀 v0.2.7 Released! Configurable Sogou-backed web search, channel tool feedback animation, linter fixes.

2026-04-23 🚀 v0.2.6 Released! Hooks with respond action and comprehensive documentation, isolation support, help banner fix.

2026-04-11 🚀 v0.2.5 Released! Zoneinfo from TZ/ZONEINFO env, Matrix CommonMark rendering alignment, read_file by lines.

2026-03-31 📱 Android Support! PicoClaw now runs on Android! Download the APK at GitHub Releases

2026-03-25 🚀 v0.2.4 Released! Agent architecture overhaul (SubTurn, Hooks, Steering, EventBus), WeChat/WeCom integration, security hardening (.security.yml, sensitive data filtering), new providers (AWS Bedrock, Azure, Xiaomi MiMo), and 35 bug fixes. PicoClaw has reached 26K Stars!

2026-03-17 🚀 v0.2.3 Released! System tray UI (Windows & Linux), sub-agent status query (spawn_status), experimental Gateway hot-reload, Cron security gating, and 2 security fixes. PicoClaw has reached 25K Stars!

2026-03-09 🎉 v0.2.1 — Biggest update yet! MCP protocol support, 4 new channels (Matrix/IRC/WeCom/Discord Proxy), 3 new providers (Kimi/Minimax/Avian), vision pipeline, JSONL memory store, model routing.

2026-02-28 📦 v0.2.0 released with Docker Compose and Web UI Launcher support.

2026-02-26 🎉 PicoClaw hits 20K Stars in just 17 days! Channel auto-orchestration and capability interfaces are live.

2026-02-16 🎉 PicoClaw breaks 12K Stars in one week! Community maintainer roles and Roadmap officially launched.

2026-02-13 🎉 PicoClaw breaks 5000 Stars in 4 days! Project roadmap and developer groups in progress.

2026-02-09 🎉 PicoClaw Released! Built in 1 day to bring AI Agents to $10 hardware with <10MB RAM. Let's Go, PicoClaw!

✨ Features

🪶 Ultra-lightweight: Recent core builds use 10–20 MB of RAM.

💰 Minimal cost: Efficient enough to run on $10 hardware — 98% cheaper than a Mac mini.

⚡️ Lightning-fast boot: 400x faster startup. Boots in <1s even on a 0.6GHz single-core processor.

🌍 Truly portable: Single binary across RISC-V, ARM, MIPS, and x86 architectures. One binary, runs everywhere!

🤖 AI-bootstrapped: Pure Go native implementation — 95% of core code was generated by an Agent and fine-tuned through human-in-the-loop review.

🔌 MCP support: Native Model Context Protocol integration — connect any MCP server to extend Agent capabilities.

🧩 Agent Plugins: Install and activate Agent Plugins 1.0.0 packages that bundle skills and MCP servers. See the plugin installation guide.

👁️ Vision pipeline: Send images and files directly to the Agent — automatic base64 encoding for multimodal LLMs.

🧠 Smart routing: Rule-based model routing — simple queries go to lightweight models, saving API costs.

*Memory use varies by build and workload. Boot speed comparison is based on 0.8GHz single-core benchmarks (see table below).

RAM: These are references, not a controlled comparison: OpenClaw's value is a deployment recommendation, NanoBot's is one Raspberry Pi 4 user report, and PicoClaw's is the estimate for recent builds.

Executable size: OpenClaw and NanoBot do not distribute the complete agent as one executable. PicoClaw's size is the measured full default macOS ARM64 build; see the measurement method and other profiles.

Hardware Compatibility List — See all tested boards, from $5 RISC-V to Raspberry Pi to Android phones. Your board not listed? Submit a PR!

🦾 Demonstration

🛠️ Standard Assistant Workflows

Full-Stack Engineer Mode	Logging & Planning	Web Search & Learning
Develop · Deploy · Scale	Schedule · Automate · Remember	Discover · Insights · Trends

🐜 Innovative Low-Footprint Deployment

PicoClaw can be deployed on virtually any Linux device!

• $9.9 LicheeRV-Nano E(Ethernet) or W(WiFi6) edition, for a minimal home assistant
• $30~50 NanoKVM, or $100 NanoKVM-Pro, for automated server operations
• $50 MaixCAM or $100 MaixCAM2, for smart surveillance

https://private-user-images.githubusercontent.com/83055338/547056448-e7b031ff-d6f5-4468-bcca-5726b6fecb5c.mp4

🌟 More Deployment Cases Await!

📦 Install

Quick install with Web UI

On Linux or macOS:

curl -fsSL https://raw.githubusercontent.com/afjcjsbx/picoclaw/main/scripts/install.sh | sh

On Windows PowerShell:

irm https://raw.githubusercontent.com/afjcjsbx/picoclaw/main/scripts/install.ps1 | iex

The installer detects the CPU architecture, verifies the release checksum, installs both binaries, and starts the launcher. The Web UI opens at http://localhost:18800; on first run, create its dashboard password in the browser.

Download precompiled binary

Download the binary for your platform from this repository's GitHub Releases.

Build from source (for development)

Prerequisites:

• Go 1.27.2+
• Node.js 22+ and pnpm 10.33.0+ for Web UI / launcher builds

git clone https://github.com/afjcjsbx/picoclaw.git

cd picoclaw
make deps

# Install frontend dependencies
(cd web/frontend && pnpm install --frozen-lockfile)

# Build the core binary for the current platform
make build

# Build the Web UI Launcher (required for WebUI mode)
make build-launcher

# Build core binaries for all Makefile-managed platforms
make build-all

# Build for Raspberry Pi Zero 2 W
# 32-bit: make build-linux-arm
# 64-bit: make build-linux-arm64
make build-pi-zero

# Build and install
make install

Raspberry Pi Zero 2 W: Use the binary that matches your OS: 32-bit Raspberry Pi OS -> make build-linux-arm; 64-bit -> make build-linux-arm64. Or run make build-pi-zero to build both.

Custom channel builds

The normal build includes every channel. Custom channel selection, optional
Seahorse builds, SQLite caveats, and measured binary sizes are documented in
the Custom Builds Guide. For example, this
builds with Telegram and Discord only:

make build GO_BUILD_TAGS='goolm,stdjson,custom_channels,channel_telegram,channel_discord'

In the measured macOS ARM64 Telegram-only build, adding no_seahorse reduced
the binary by 3.92 MiB (14.3%). See the guide for the full measurement details
and the cases where Matrix or WhatsApp Native still require SQLite.

🚀 Quick Start Guide

🌐 WebUI Launcher (Recommended for Desktop)

The WebUI Launcher provides a browser-based interface for configuration and chat. This is the easiest way to get started — no command-line knowledge required.

Option 1: Double-click (Desktop)

After downloading from GitHub Releases, double-click picoclaw-launcher (or picoclaw-launcher.exe on Windows). Your browser will open automatically at http://localhost:18800.

Option 2: Command line

picoclaw-launcher
# Open http://localhost:18800 in your browser

[!TIP]
Remote access / Docker / VM: Add the -public flag to listen on all interfaces:

picoclaw-launcher -public

Getting started:

Open the WebUI, then: 1) Configure a Provider (add your LLM API key) -> 2) Configure a Channel (e.g., Telegram) -> 3) Start the Gateway -> 4) Chat!

For detailed WebUI documentation, see PicoClaw documentation.

Docker (alternative)

# 1. Clone this repo
git clone https://github.com/afjcjsbx/picoclaw.git
cd picoclaw

# 2. First run — auto-generates docker/data/config.json then exits
#    (only triggers when both config.json and workspace/ are missing)
docker compose -f docker/docker-compose.yml --profile launcher up
# The container prints "First-run setup complete." and stops.

# 3. Set your API keys
vim docker/data/config.json

# 4. Start
docker compose -f docker/docker-compose.yml --profile launcher up -d
# Open http://localhost:18800

Docker / VM users: The Gateway listens on 127.0.0.1 by default. Set PICOCLAW_GATEWAY_HOST=0.0.0.0 or use the -public flag to make it accessible from the host.

# Check logs
docker compose -f docker/docker-compose.yml logs -f

# Stop
docker compose -f docker/docker-compose.yml --profile launcher down

# Update
docker compose -f docker/docker-compose.yml pull
docker compose -f docker/docker-compose.yml --profile launcher up -d

macOS — First Launch Security Warning

macOS may block picoclaw-launcher on first launch because it is downloaded from the internet and not notarized through the Mac App Store.

Step 1: Double-click picoclaw-launcher. You will see a security warning:

"picoclaw-launcher" Not Opened — Apple could not verify "picoclaw-launcher" is free of malware that may harm your Mac or compromise your privacy.

Step 2: Open System Settings → Privacy & Security → scroll down to the Security section → click Open Anyway → confirm by clicking Open Anyway in the dialog.

After this one-time step, picoclaw-launcher will open normally on subsequent launches.

🔌 Providers (LLM)

Show 30+ supported providers and configuration

PicoClaw supports 30+ LLM providers through the model_list configuration. Use the protocol/model format:

Provider	Protocol	API Key	Notes
OpenAI	openai/	Required	GPT-5.4, GPT-4o, o3, etc.
Anthropic	anthropic/	Required	Claude Opus 4.6, Sonnet 4.6, etc.
Google Gemini	gemini/	Required	Gemini 3 Flash, 2.5 Pro, etc.
OpenRouter	openrouter/	Required	200+ models, unified API
Zhipu (GLM)	zhipu/	Required	GLM-4.7, GLM-5, etc.
DeepSeek	deepseek/	Required	DeepSeek-V3, DeepSeek-R1
Volcengine	volcengine/	Required	Doubao, Ark models
Qwen	qwen/	Required	Qwen3, Qwen-Max, etc.
Groq	groq/	Required	Fast inference (Llama, Mixtral)
Moonshot (Kimi)	moonshot/	Required	Kimi models
Minimax	minimax/	Required	MiniMax models
Mistral	mistral/	Required	Mistral Large, Codestral
NVIDIA NIM	nvidia/	Required	NVIDIA hosted models
Cerebras	cerebras/	Required	Fast inference
NEAR AI Cloud	nearai/	Required	TEE inference, OpenAI-compatible
Novita AI	novita/	Required	Various open models
Xiaomi MiMo	mimo/	Required	MiMo models
Ollama	ollama/	Not needed	Local models, self-hosted
vLLM	vllm/	Not needed	Local deployment, OpenAI-compatible
LiteLLM	litellm/	Varies	Proxy for 100+ providers
Azure OpenAI	azure/	API key or Entra ID**	Enterprise Azure deployment
GitHub Copilot	github-copilot/	OAuth	Device code login
Antigravity	antigravity/	OAuth	Google Cloud AI
AWS Bedrock*	bedrock/	AWS credentials	Claude, Llama, Mistral on AWS

* AWS Bedrock requires build tag: go build -tags bedrock. Set api_base to a region name (e.g., us-east-1) for automatic endpoint resolution across all AWS partitions (aws, aws-cn, aws-us-gov). When using a full endpoint URL instead, you must also configure AWS_REGION via environment variable or AWS config/profile.

** Azure OpenAI uses api_key when set. If api_key is omitted, the provider falls back to Microsoft Entra ID via DefaultAzureCredential (env vars, workload identity, managed identity, Azure CLI, etc.). The Entra ID path requires build tag: go build -tags azidentity.

Local deployment (Ollama, vLLM, etc.)

Ollama:

{
  "model_list": [
    {
      "model_name": "local-llama",
      "model": "ollama/llama3.1:8b",
      "api_base": "http://localhost:11434/v1"
    }
  ]
}

vLLM:

{
  "model_list": [
    {
      "model_name": "local-vllm",
      "model": "vllm/your-model",
      "api_base": "http://localhost:8000/v1"
    }
  ]
}

For full provider configuration details, see Providers & Models.

💬 Channels (Chat Apps)

Show 19+ supported channels and setup guides

Talk to your PicoClaw through 19+ messaging platforms:

Channel	Setup	Protocol	Docs
Telegram	Easy (bot token)	Long polling	Guide
Discord	Easy (bot token + intents)	WebSocket	Guide
WhatsApp	Easy (QR scan or bridge URL)	Native / Bridge	Guide
Weixin	Easy (Native QR scan)	iLink API	Guide
QQ	Easy (AppID + AppSecret)	WebSocket	Guide
Slack	Easy (bot + app token)	Socket Mode	Guide
Matrix	Medium (homeserver + token)	Sync API	Guide
Delta Chat	Easy (chatmail or existing account)	JSON-RPC (email/E2EE)	Guide
DingTalk	Medium (client credentials)	Stream	Guide
Feishu / Lark	Medium (App ID + Secret)	WebSocket/SDK	Guide
LINE	Medium (credentials + webhook)	Webhook	Guide
WeCom	Easy (QR login or manual)	WebSocket	Guide
VK	Easy (group token)	Long Poll	Guide
IRC	Medium (server + nick)	IRC protocol	Guide
OneBot	Medium (WebSocket URL)	OneBot v11	Guide
MQTT	Easy (broker + agent_id)	MQTT pub/sub	Guide
MaixCam	Easy (enable)	TCP socket	Guide
Pico	Easy (enable)	Native protocol	Built-in
Pico Client	Easy (WebSocket URL)	WebSocket	Built-in

All webhook-based channels share a single Gateway HTTP server (gateway.host:gateway.port, default 127.0.0.1:18790). Feishu uses WebSocket/SDK mode and does not use the shared HTTP server.

Log verbosity is controlled by gateway.log_level (default: warn). Supported values: debug, info, warn, error, fatal. Can also be set via PICOCLAW_LOG_LEVEL. See Configuration for details.

For detailed channel setup instructions, see Chat Apps Configuration.

🔧 Tools

🔍 Web Search

Show supported search engines and free tiers

PicoClaw can search the web to provide up-to-date information. Configure in tools.web:

Search Engine	API Key	Free Tier	Link
DuckDuckGo	Not needed	Unlimited	Built-in fallback
Gemini Google Search	Required	Varies	Gemini with Google Search grounding
Baidu Search	Required	1500/month (daily allocation)	AI-powered, China-optimized
Tavily	Required	1000 queries/month	Optimized for AI Agents
Brave Search	Required	2000 queries/month	Fast and private
Kagi Search	Required	Paid/limited by API setup	Premium search results
Keenable	Optional	Keyless: 10 req/s, 1000/hour per IP	Works without a key; a key lifts the rate limits
Perplexity	Required	Paid	AI-powered search
SearXNG	Not needed	Self-hosted	Free metasearch engine
GLM Search	Required	Varies	Zhipu web search

⚙️ Other Tools

PicoClaw includes built-in tools for file operations, code execution, scheduling, and more. See Tools Configuration for details.

🎯 Skills

Skills and MCP servers can also be packaged together as portable Agent Plugins 1.0.0.
See the plugin guide and the
working demo plugin.
Mem0 publishes its own
Agent Plugin;
see the compatibility notes before enabling it.

Skills are modular capabilities that extend your Agent. They are loaded from SKILL.md files in your workspace.

Install skills from ClawHub:

picoclaw skills search "web scraping"
picoclaw skills install <skill-name>

Configure skill registries:

Add to your config.json:

{
  "tools": {
    "skills": {
      "registries": {
        "clawhub": {
          "auth_token": "your-clawhub-token"
        },
        "github": {
          "base_url": "https://github.com",
          "auth_token": "your-github-token",
          "proxy": ""
        }
      }
    }
  }
}

tools.skills.github.* is deprecated. Use tools.skills.registries.github.* instead.

For more details, see Tools Configuration - Skills.

🔗 MCP (Model Context Protocol)

PicoClaw natively supports MCP — connect any MCP server to extend your Agent's capabilities with external tools and data sources.

PicoClaw is a lightweight assistant, so remote MCP servers are the best choice. For local servers, prefer natively compiled server binaries and avoid npx, uvx, or other heavyweight dependency managers.

{
  "tools": {
    "mcp": {
      "enabled": true,
      "servers": {
        "browserbase": {
          "enabled": true,
          "deferred": false,
          "command": "",
          "type": "http",
          "url": "https://mcp.browserbase.com/mcp?browserbaseApiKey=API_KEY",
          "headers": {
            "BROWSERBASE_PROJECT_ID": "********"
          }
        }
      }
    }
  }
}

You can manage common MCP setups directly from the CLI instead of editing JSON by hand:

picoclaw mcp list
picoclaw mcp test browserbase

picoclaw mcp is a configuration manager: it updates config.json under tools.mcp.servers, but it does not keep the server process running itself.

Use picoclaw mcp edit when you need advanced fields that are not covered by picoclaw mcp add.
For example, picoclaw mcp add supports --deferred and --env-file, while picoclaw mcp edit is still useful for direct JSON editing and uncommon MCP settings.

For full MCP configuration (stdio, SSE, HTTP transports, Tool Discovery), see Tools Configuration - MCP. For CLI usage and examples, see MCP Server CLI.

Join the Agent Social Network

Connect PicoClaw to the Agent Social Network simply by sending a single message via the CLI or any integrated Chat App.

Read https://clawdchat.ai/skill.md and follow the instructions to join ClawdChat.ai

🖥️ CLI Reference

Command	Description
picoclaw onboard	Initialize config & workspace
picoclaw auth weixin	Connect WeChat account via QR
picoclaw agent -m "..."	Chat with the agent
picoclaw agent	Interactive chat mode
picoclaw gateway	Start the gateway
picoclaw status	Show status
picoclaw version	Show version info
picoclaw model	View or switch the default model
picoclaw mcp list	List configured MCP servers
picoclaw mcp add ...	Add or update an MCP server entry
picoclaw mcp test	Probe a configured MCP server
picoclaw mcp edit	Open config for advanced MCP editing
picoclaw mcp remove	Remove an MCP server entry
picoclaw cron list	List all scheduled jobs
picoclaw cron add ...	Add a scheduled job
picoclaw cron disable	Disable a scheduled job
picoclaw cron remove	Remove a scheduled job
picoclaw skills list	List installed skills
picoclaw skills install	Install a skill
picoclaw migrate	Migrate data from older versions
picoclaw auth login	Authenticate with providers

⏰ Scheduled Tasks / Reminders

PicoClaw supports scheduled reminders and recurring tasks through the cron tool:

• One-time reminders: "Remind me in 10 minutes" -> triggers once after 10min
• Recurring tasks: "Remind me every 2 hours" -> triggers every 2 hours
• Cron expressions: "Remind me at 9am daily" -> uses cron expression

See docs/reference/cron.md for current schedule types, execution modes, command-job gates, and persistence details.

📚 Documentation

For detailed guides beyond this README:

Topic	Description
Docker & Quick Start	Docker Compose setup, Launcher/Agent modes
Chat Apps	All 18+ channel setup guides
Configuration	Environment variables, workspace layout, security sandbox
Plugin Installation	Install and activate Agent Plugin packages
MCP Server CLI	Add, list, test, edit, and remove MCP server entries from the CLI
Scheduled Tasks and Cron Jobs	Cron schedule types, deliver modes, command gates, job storage
Providers & Models	30+ LLM providers, model routing, model_list configuration
Spawn & Async Tasks	Quick tasks, long tasks with spawn, async sub-agent orchestration
Hooks	Event-driven hook system: observers, interceptors, approval hooks
Steering	Inject messages into a running agent loop between tool calls
SubTurn	Subagent coordination, concurrency control, lifecycle
Troubleshooting	Common issues and solutions
Tools Configuration	Per-tool enable/disable, exec policies, MCP, Skills
Hardware Compatibility	Tested boards, minimum requirements

🤝 Contribute & Roadmap

PRs welcome! The codebase is intentionally small and readable.

See our CONTRIBUTING.md for guidelines.