sipeed/picoclaw

Tiny, Fast, and Deployable anywhere — automate the mundane, unleash your creativity

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 12 minutes ago
Added to GitGenius on August 31st, 2026
Created on February 4th, 2026
Open Issues & Pull Requests: 36 (+0)
Number of forks: 4,462
Total Stargazers: 29,919 (+1)
Total Subscribers: 171 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 13.0 hours
Mean response time: 2.9 days
90th percentile: 8.4 days
Tracked items: 709

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 96% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 10% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 26
New in 7 days: 5
Closed in 7 days: 4
Avg open age: 109 days
Stale 30+ days: 13
Stale 90+ days: 11

Recent activity

Opened in 7 days: 5
Closed in 7 days: 4
Comments in 7 days: 1
Events in 7 days: 1

Top labels

  • type: bug (344)
  • type: enhancement (232)
  • stale (190)
  • domain: provider (149)
  • domain: channel (141)
  • domain: config (104)
  • domain: agent (88)
  • domain: tool (66)

Detailed Description

PicoClaw is an ultra-lightweight personal AI assistant written in Go that runs on minimal hardware with extremely low memory footprint.

The project addresses the challenge of deploying AI assistants on resource-constrained devices. Rather than adapting existing solutions, PicoClaw was built from the ground up in Go, reportedly using a self-bootstrapping process where an AI agent drove architectural decisions and code optimization. The tool targets scenarios where traditional AI assistants are impractical due to hardware limitations or cost, enabling deployment on devices with under 10MB of RAM and hardware costing around ten dollars.

PicoClaw suits developers and organizations needing AI assistance on edge devices, embedded systems, or severely resource-limited environments where conventional solutions prove prohibitively expensive or memory-intensive. The project explicitly positions itself as an independent implementation rather than a fork of existing projects. Adoption requires awareness that the project remains in early development stages, with a security notice cautioning against production deployment before reaching version 1.0. Recent development has increased memory usage to 10-20MB as features have been added, with resource optimization planned for later phases.

The project maintains active development across multiple communication channels including Discord and WeChat communities, with documentation and wiki resources available. The codebase supports multiple architectures including x86-64, ARM64, MIPS, RISC-V, and LoongArch, indicating broad hardware compatibility work. Official communication emphasizes security awareness, particularly warning against fraudulent cryptocurrency claims and third-party domain registrations using variations of the official domain.