HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
sipeed
picoclaw
Go2026–2026
sipeed / picoclaw

picoclaw

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

14Distinct people
14Mentions
1Explicit recommenders
30.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

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

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

This is a great point, analogous to the https://boringtechnology.club/ philosophy I've come to love. There's no reason we need to make an incredibly intelligent shell execution…

schrodinger used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week14 dated mentions

Observed mentions: 2026-02-09 15:23:37 UTC to 2026-09-13 19:35:34 UTC. Weeks start Monday, UTC.

02462026-02-09 00:00:00 UTC to 2026-02-16 00:00:00 UTC (exclusive): 6 mentions; 6 submissions, 0 commentsFeb 92026-02-16 00:00:00 UTC to 2026-02-23 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2026-02-23 00:00:00 UTC to 2026-03-02 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-03-02 00:00:00 UTC to 2026-03-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-09 00:00:00 UTC to 2026-03-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-16 00:00:00 UTC to 2026-03-23 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-03-23 00:00:00 UTC to 2026-03-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-30 00:00:00 UTC to 2026-04-06 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-04-06 00:00:00 UTC to 2026-04-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-13 00:00:00 UTC to 2026-04-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-20 00:00:00 UTC to 2026-04-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-27 00:00:00 UTC to 2026-05-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-04 00:00:00 UTC to 2026-05-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-11 00:00:00 UTC to 2026-05-18 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-05-18 00:00:00 UTC to 2026-05-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-25 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMay 252026-06-01 00:00:00 UTC to 2026-06-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-08 00:00:00 UTC to 2026-06-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-15 00:00:00 UTC to 2026-06-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-22 00:00:00 UTC to 2026-06-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-29 00:00:00 UTC to 2026-07-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-06 00:00:00 UTC to 2026-07-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-13 00:00:00 UTC to 2026-07-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-20 00:00:00 UTC to 2026-07-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-27 00:00:00 UTC to 2026-08-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-03 00:00:00 UTC to 2026-08-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-10 00:00:00 UTC to 2026-08-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-17 00:00:00 UTC to 2026-08-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-24 00:00:00 UTC to 2026-08-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-31 00:00:00 UTC to 2026-09-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-07 00:00:00 UTC to 2026-09-14 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsSep 7

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 92026-02-09 00:00:00 UTC2026-02-16 00:00:00 UTC660
Feb 162026-02-16 00:00:00 UTC2026-02-23 00:00:00 UTC303
Feb 232026-02-23 00:00:00 UTC2026-03-02 00:00:00 UTC110
Mar 22026-03-02 00:00:00 UTC2026-03-09 00:00:00 UTC000
Mar 92026-03-09 00:00:00 UTC2026-03-16 00:00:00 UTC000
Mar 162026-03-16 00:00:00 UTC2026-03-23 00:00:00 UTC110
Mar 232026-03-23 00:00:00 UTC2026-03-30 00:00:00 UTC000
Mar 302026-03-30 00:00:00 UTC2026-04-06 00:00:00 UTC110
Apr 62026-04-06 00:00:00 UTC2026-04-13 00:00:00 UTC000
Apr 132026-04-13 00:00:00 UTC2026-04-20 00:00:00 UTC000
Apr 202026-04-20 00:00:00 UTC2026-04-27 00:00:00 UTC000
Apr 272026-04-27 00:00:00 UTC2026-05-04 00:00:00 UTC000
May 42026-05-04 00:00:00 UTC2026-05-11 00:00:00 UTC000
May 112026-05-11 00:00:00 UTC2026-05-18 00:00:00 UTC101
May 182026-05-18 00:00:00 UTC2026-05-25 00:00:00 UTC000
May 252026-05-25 00:00:00 UTC2026-06-01 00:00:00 UTC000
Jun 12026-06-01 00:00:00 UTC2026-06-08 00:00:00 UTC000
Jun 82026-06-08 00:00:00 UTC2026-06-15 00:00:00 UTC000
Jun 152026-06-15 00:00:00 UTC2026-06-22 00:00:00 UTC000
Jun 222026-06-22 00:00:00 UTC2026-06-29 00:00:00 UTC000
Jun 292026-06-29 00:00:00 UTC2026-07-06 00:00:00 UTC000
Jul 62026-07-06 00:00:00 UTC2026-07-13 00:00:00 UTC000
Jul 132026-07-13 00:00:00 UTC2026-07-20 00:00:00 UTC000
Jul 202026-07-20 00:00:00 UTC2026-07-27 00:00:00 UTC000
Jul 272026-07-27 00:00:00 UTC2026-08-03 00:00:00 UTC000
Aug 32026-08-03 00:00:00 UTC2026-08-10 00:00:00 UTC000
Aug 102026-08-10 00:00:00 UTC2026-08-17 00:00:00 UTC000
Aug 172026-08-17 00:00:00 UTC2026-08-24 00:00:00 UTC000
Aug 242026-08-24 00:00:00 UTC2026-08-31 00:00:00 UTC000
Aug 312026-08-31 00:00:00 UTC2026-09-07 00:00:00 UTC000
Sep 72026-09-07 00:00:00 UTC2026-09-14 00:00:00 UTC101

What Hacker News says

14 sources
schrodinger·Sep 13, 2026Recommendation phrase
This is a great point, analogous to the https://boringtechnology.club/ philosophy I've come to love. There's no reason we need to make an incredibly intelligent shell execution engine that can identify patterns that seem evil and may represent unwanted behavior to solve this problem. Simply limiting the available tools to a finite, known, ironclad-secure set (even if it's quite sprawling) is sufficient. LLMs will still find workarounds — from what I understand, a large part of the issue in this situation was that an agent was presumed to have read-only Internet access because it could only make GET requests. It should be pretty obvious that there's at least one website on the Internet that allows writes via GET. I think this is where auditing comes in, and a live team of people watching tool calls would have noticed the strange behavior.
Read the rest
But I think a lot of times people jump to overly complex solutions when simple, well-bounded ones would work just fine. Yes, the intelligent shell is a great goal, but it's akin to solving the halting problem. This philosophy is what I love about PicoClaw (https://github.com/sipeed/picoclaw), and incidentally the philosophy behind Go and even *nix in general (i.e. provide small, composable, single-purpose tools).
In Why are AI agents lying, cheating and coordinating?
snthpy·Mar 16, 2026Submission

Ask HN: AI Agents vs. Gateways vs. Harnesses

Hi, I'd like to get everyone's take on the different components in the AI Agents ecoysystem. I find the current terminology quite confusing as it's not always obvious what I'll be actually getting when I examine the available options. A lot of things get called Agents, but that term seems hard to define as it often refers to overlapping functionality. To me, agents seem to be currently composed of the following components: ## Harnesses - Adds UI and system instructions around an LLM and may also augment it with tools such as memory, tool calls, etc... - Examples are Claude Code, Code, Gemini CLI, pi.dev, ... ## Gateways - These connect agents to your communication tool of choice, e.g. Whatsapp, Telegram, Slack, Discord, ... - Examples are OpenClaw and Nanoclaw ## Sandboxes - Isolated environments where Agents can run with limited or audit
Read the rest
able capabilities - Examples can be from physical ones like separate Mac Minis to docker-agent, agent-sandbox, localsandbox, ... This then takes us to *Agents*: ## Agents - AI Systems capable of exercising some agency, i.e. non-zero amounts of autonomous behaviour without a human-in-the-loop. - These usually combine the following components: - **LLM**: to provide the intelligence/reasoning/decision making - **Harness**: to steer the behaviour and enable long-term coherence of actions beyond the limits of current context windows - **Gateway**: to interact with humans and/or other agents - **Sandbox**: that aims to limit the capabilities of the Agent to a sanctioned set of safe operations for the agent to execute autonomously. My issue is that when I look at the available options, it's generally not clear to me which components I am getting: - https://github.com/openclaw/openclaw: Typescript, The OG, one-stop solution, easiest to install but apparently a bit of a Frankenmonster and complex - https://github.com/qwibitai/nanoclaw: Typescript, gaining popularity, minimalist, implementation seems reliant on Claude Code to handle install and configuration - https://github.com/sipeed/picoclaw: Golang - https://github.com/zeroclaw-labs/zeroclaw: Rust - https://github.com/nullclaw/nullclaw: Zig - https://nemoclaw.bot/: By Nvidia, claims to be open source "based", but I couldn't find a repo What I would really like is to be able to assemble my own stack of Sandbox + Gateway + Harness + LLM. Thoughts/recommendations?
1 points · Open discussion

Show HN: PicoClaw 10MB OpenClaw alternative that runs AI agents on $10 hardware

OpenClaw is great, but it’s fairly heavy to run 24/7 at home. In practice it often needs >1GB RAM and a small server or Mac mini, which makes “personal AI agents” surprisingly expensive. I recently came across PicoClaw, an open-source project by Sipeed that takes a very different approach. Instead of running large runtimes locally, it acts as a lightweight agent client and delegates reasoning to cloud LLM APIs (GLM/GPT/Claude), while keeping orchestration local. The interesting part is the footprint: < 10MB memory usage < 1s cold start single self-contained binary no Node.js or Python runs on ARM / x86 / RISC-V So it can run on devices like Raspberry Pi 3B, cheap RISC-V boards (~$10), old Android TV boxes, etc. Technically it’s rebuilt from scratch in Go, which explains most of the startup and memory improvements. No dependency tree, no r
Read the rest
untime environment — just one binary. Despite the size, it still supports: shell execution file operations web search speech-to-text Telegram / Discord / QQ / DingTalk integrations Quick start is basically: git clone https://github.com/sipeed/picoclaw.git cd picoclaw make build ./picoclaw agent Feels more like a “microkernel” approach to agents compared to heavier stacks. Interesting direction if you’re experimenting with edge AI or home lab automation. Repo: https://github.com/sipeed/picoclaw Site: https://picoclaw.org/
2 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.