Index / LettaBot · updated Aug 17, 2026
LettaBot
letta-ai/lettabot · abandoned · rank 32 of 43 by stars
A now-deprecated multi-channel AI assistant with persistent unified memory across Telegram, Slack, Discord, WhatsApp, and Signal. All active development has moved into 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 — 15 months old (dated in the model id)
Pin last edited 7 months ago
Evidence
Decision
Why choose LettaBot over OpenClaw?
Why choose this
- Unified persistent memory across five chat platforms in a single agent instance
- Built-in Bluesky Jetstream feed ingestion for social media monitoring
- Voice message transcription via OpenAI Whisper out of the box
Tradeoffs
- Officially deprecated — no new features, bug fixes, or security patches
- Requires a Letta API key or self-hosted Letta server (platform lock-in)
- Node.js/TypeScript stack has higher memory footprint than OpenClaw's Rust/Go alternatives
Best fit
- Existing LettaBot users maintaining legacy deployments
- Studying the architecture of a multi-channel agent before migrating to Letta Code Channels
- Reference for Bluesky Jetstream feed ingestion patterns
Avoid if
- Starting any new project — officially deprecated and replaced by Letta Code Channels
- You need active maintenance, security patches, or community support
- You want a production-ready, always-on agent with modern scheduling (use Letta Code Remote Environments instead)
High confidence in deprecation status based on explicit README warning and archived repo state. Low community sentiment due to zero Reddit mentions and minimal web footprint beyond directory listings. Evidence is strong from primary sources (README, commits, release tags) but thin on community validation.
AI layer reviewed Aug 2, 2026 · how this is written
Star activity
327 stars today
Overview
LettaBot is a TypeScript-based personal AI assistant that connects a single Letta agent to multiple messaging platforms — Telegram, Slack, Discord, WhatsApp, and Signal — while maintaining unified persistent memory across all channels. Built on the Letta Code SDK, it also supports Bluesky Jetstream feed ingestion for social media monitoring, voice message transcription via OpenAI Whisper, and local tool execution including file reading, code search, and shell command execution on the host machine. The architecture is designed around a single agent ID that persists across sessions, with streaming responses and periodic heartbeat check-ins.
As of early 2026, LettaBot has been officially deprecated and archived. All active development has moved into Letta Code's native Channels feature (for messaging platform integration) and Remote Environments (for always-on server deployments). The deprecation commit (#702) explicitly redirects users to these newer, more integrated alternatives. Existing deployments continue to function, but the project will receive no further updates, security patches, or community support.
Compared to OpenClaw, LettaBot was more narrowly focused on the Letta platform ecosystem rather than being a general-purpose, platform-agnostic assistant framework. Its multi-channel memory unification was a standout feature, but the deprecation means it now serves primarily as a reference architecture rather than a viable production tool. The migration path to Letta Code Channels is documented as straightforward (~20 minutes), making the codebase useful for understanding patterns but not for new deployments.