You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 26, 2026. It is now read-only.
Telegram / Slack messaging → Channels — same agent, same memory, integrated into Letta Code directly
Always-on agent on a VPS or server → Remote Environments — letta server uses outbound WebSocket, no ports to open, no reverse proxy needed
Heartbeats and scheduled tasks → letta cron — built into remote environments
Existing LettaBot deployments will continue to function, but for any new project, use Channels + Remote Environments. Migration is typically straightforward (~20 minutes).
Need migration help? Ask in the #ezra channel on the Letta Discord.
Warning
LettaBot is no longer actively maintained. All new development is happening in Letta Code via Channels and Remote Environments.
Where to go instead:
letta serveruses outbound WebSocket, no ports to open, no reverse proxy neededExisting LettaBot deployments will continue to function, but for any new project, use Channels + Remote Environments. Migration is typically straightforward (~20 minutes).
Need migration help? Ask in the
#ezrachannel on the Letta Discord.