# LettaBot vs OpenClaw

> Side-by-side comparison of two projects in the OpenClaw ecosystem.

Canonical HTML: https://shelldex.com/compare/lettabot-vs-openclaw/
JSON: https://shelldex.com/api/compare/lettabot-vs-openclaw.json

| Field | LettaBot | OpenClaw |
| --- | --- | --- |
| Tagline | Persistent-memory agent across 5 messaging channels | The OG self-hosted AI super-agent |
| Language | typescript | typescript |
| Status | active | active |
| Stars | 328 | 372k |
| Forks | 88 | 77049 |
| Open issues | 85 | 7041 |
| License | Apache-2.0 | MIT |
| Last commit | 2026-05-03T23:21:29Z | 2026-05-15T16:50:31Z |
| 7d growth | 3 | 3106 |
| MCP support | no | yes |
| Requires LLM | yes | yes |
| Platforms | server | server |
| Categories | memory, messaging | reference, self-hosted |
| Health score | 35/100 | 95/100 |
| Leaderboard rank | #37 | #1 |

## Key differences

- OpenClaw has 1135x more stars (372k vs 328), indicating significantly broader adoption.
- OpenClaw is growing faster with +3.1k stars this week vs +3 for LettaBot.
- OpenClaw was updated today, while LettaBot's last commit was 11 days ago.
- LettaBot uses the Apache-2.0 license while OpenClaw uses MIT.
- OpenClaw has MCP (Model Context Protocol) support while LettaBot does not.
- LettaBot focuses on memory, messaging while OpenClaw targets reference, self-hosted.

## Descriptions

### LettaBot

Personal AI assistant that remembers everything across Telegram, Slack, Discord, WhatsApp, and Signal. Unified memory, heartbeat check-ins, voice transcription, and scheduling — powered by the Letta SDK.

### OpenClaw

The original. Self-hosted AI super-agent platform. Formerly Clawdbot, then Moltbot. The project that started it all.