Index / LettaBot · updated Sep 4, 2026
LettaBot
letta-ai/lettabot · abandoned · rank 32 of 43 by stars
A multi-channel personal AI assistant with unified persistent memory across Telegram, Slack, Discord, WhatsApp, and Signal. Now officially deprecated and archived, replaced by Letta Code's Channels and Remote Environments.
Facts
Repository
Runtime
Posture
Community
Security breakdown
Composite 55 / 100 · how these are scored
higher is safer
higher is safer
higher is safer
higher is safer
higher is riskier
Model access
Read from the repository, not written by a model · 60 files examined
2 providers · custom endpoint
Pinned models
claude-sonnet-4-20250514 released 2025-05-14 — 16 months old (dated in the model id)
Pin last edited 7 months ago
Evidence
Decision
Why choose LettaBot over OpenClaw?
Why choose this
- Unified memory across five chat platforms plus Bluesky ingestion
- Built-in voice transcription via Whisper
- One-click Railway deployment template
Tradeoffs
- Officially deprecated and archived with no future development
- No active skill/plugin ecosystem comparable to ClawHub
- Local shell access with limited sandboxing
Best fit
- Existing deployments that still work and need short-term continuity
- Developers studying a hackable multi-channel agent reference implementation
- Users planning migration to Letta Code Channels
Avoid if
- You are starting a new project (use Letta Code Channels instead)
- You need active maintenance and security patches
- You want a supported long-term deployment
Evidence is strong that this project is deprecated: the README explicitly marks it archived and points to Letta Code replacements. Web footprint is thin (no Reddit mentions), so community sentiment is inferred mostly from the deprecation notice and awesome-list references.
AI layer reviewed Aug 24, 2026 · how this is written
Star activity
327 stars today
Overview
LettaBot was a personal AI assistant built on the Letta Code SDK, designed to live across Telegram, Slack, Discord, WhatsApp, and Signal with a single unified agent memory. It supported persistent long-term memory across sessions, local tool execution (file reads, code search, shell commands), voice message transcription via OpenAI Whisper, heartbeat check-ins, scheduling, and read-only Bluesky Jetstream feed ingestion. Deployment was streamlined via a Railway template and YAML configuration.
The project is now officially deprecated and archived. The maintainers direct all new users to Letta Code's Channels (for messaging integrations), Remote Environments (for always-on VPS agents via outbound WebSocket), and letta cron (for scheduling). Existing deployments continue to function, and migration is described as taking roughly 20 minutes.
Compared to OpenClaw, LettaBot offered a polished multi-channel memory-centric experience backed by Letta's agent infrastructure, but it lacked a community skill registry and is no longer maintained. It is best treated as a reference implementation or a migration starting point rather than a viable OpenClaw alternative going forward.