headlongPersistent-agency agent harness in ~10K lines of Bash: it keeps thinking between messages, thinks by writing shell commands, and one shared mind serves a whole team over Slack or Telegram.
Why switchBoth are self-hosted always-on personal agents with persistent memory and IM channels. Picobot is a 9MB Go binary with 16 fixed tools that runs on a $5 VPS; Headlong is Bash all the way down, has no tool system, and thinks continuously instead of on triggers.
Full comparison → mateclawSelf-hosted Java agent platform: ReAct plus plan-and-execute 'digital employees' with an LLM Wiki knowledge layer, skills/MCP/ACP tools, approval-gated actions and eight IM channels in one JAR.
Why switchSame shape — personal agent on your own box with memory, skills, MCP and chat channels — at opposite scales: picobot is a 9MB Go binary on a $5 VPS, MateClaw a Spring Boot deployment with multi-user workspaces and consoles.
Full comparison → openworkerAndrew Ng's local-first desktop AI coworker: give it an outcome and it works across your files, terminal and 25+ apps — Slack, Jira, Notion, Gmail — then hands back the finished deliverable.
Why switchSame 'agent that just runs your errands' idea, different host: picobot is a 9MB Go binary on a $5 VPS reachable from Telegram or Slack, openworker a local-first desktop coworker driving your files, terminal and 25+ apps.
Full comparison → coreSelf-hosted, always-on "personal AI OS": watches your apps, keeps a persistent memory graph, and acts autonomously within guardrails — a product, not a library for building agents.
Why switchBoth are always-on self-hosted personal AI assistants with persistent memory, at opposite ends of the weight spectrum: core is a full 'personal AI OS' product watching your apps; Picobot is a 9MB binary you leave running on a $5 VPS and message from Telegram.
Full comparison →