Fix: Resolve main.js path relative to CLI file, not cwd
LettaBot
Your personal AI assistant that remembers everything across Telegram, Slack, Discord, WhatsApp, and Signal. Powered by the Letta Code SDK.
Features
- Multi-Channel - Chat seamlessly across Telegram, Slack, Discord, WhatsApp, and Signal
- Unified Memory - Single agent remembers everything from all channels
- Persistent Memory - Agent remembers conversations across sessions (days/weeks/months)
- Local Tool Execution - Agent can read files, search code, run commands on your machine
- Heartbeat - Periodic check-ins where the agent reviews tasks
- Scheduling - Agent can create one-off reminders and recurring tasks
- Streaming Responses - Real-time message updates as the agent thinks
Quick Start
Prerequisites
- Node.js 18+
- A Letta API key from app.letta.com (or a running Letta Docker server)
- A Telegram bot token from @BotFather
Install
# Clone the repository
git clone https://github.com/letta-ai/lettabot.git
cd lettabot
# Install dependencies
npm install
# Build and link the CLI globally
npm run build
npm link
Optional: Run a Letta Docker server
You can use lettabot with a Docker server with:
docker run \
-v ~/.letta/.persist/pgdata:/var/lib/postgresql/data \
-p 8283:8283 \
-e OPENAI_API_KEY="your_openai_api_key" \
letta/letta:latest
See the documentation for more details on running with Docker.
Setup
Run the interactive onboarding wizard:
lettabot onboard
Run
lettabot server
That's it! Message your bot on Telegram.
Skills
LettaBot is compatible with skills.sh and Clawdhub.
# from Clawdhub
npx molthub@latest install sonoscli
# from skills.sh
npm run skills:add supabase/agent-skills
# connect to LettaBot
lettabot skills
◆ Enable skills (space=toggle, enter=confirm):
│ ◻ ── ClawdHub Skills ── (~/clawd/skills)
│ ◻ 🦞 sonoscli
│ ◻ ── Vercel Skills ── (~/.agents/skills)
│ ◻ 🔼 supabase/agent-skills
│ ◻ ── Built-in Skills ──
│ ◻ 📦 1password
│ ◻ ...
# View LettaBot skills
lettabot skills status
Home Assistant
Control your smart home with LettaBot:
# 1. Install the skill from ClawdHub
npx clawdhub@latest install homeassistant
# 2. Enable the skill
lettabot skills sync
# Select "homeassistant" from the list
# 3. Configure credentials (see skill docs for details)
# You'll need: HA URL + Long-Lived Access Token
Then ask your bot things like:
- "Turn off the living room lights"
- "What's the temperature in the bedroom?"
- "Set the thermostat to 72"
CLI Commands
| Command | Description |
|---|---|
lettabot onboard |
Interactive setup wizard |
lettabot server |
Start the bot server |
lettabot configure |
View and edit configuration |
lettabot skills status |
Show enabled and available skills |
lettabot destroy |
Delete all local data and start fresh |
lettabot help |
Show help |
Channel Setup
LettaBot uses a single agent with a single conversation across all channels:
Telegram ──┐
Slack ─────┤
Discord ───┼──→ ONE AGENT ──→ ONE CONVERSATION
WhatsApp ──┤ (memory) (chat history)
Signal ────┘
- Start a conversation on Telegram
- Continue it on Slack
- Pick it up on WhatsApp
- The agent remembers everything!
| Channel | Guide | Requirements |
|---|---|---|
| Telegram | Setup Guide | Bot token from @BotFather |
| Slack | Setup Guide | Slack app with Socket Mode |
| Discord | Setup Guide | Discord bot + Message Content Intent |
| Setup Guide | Phone with WhatsApp | |
| Signal | Setup Guide | signal-cli + phone number |
At least one channel is required. Telegram is the easiest to start with.
Bot Commands
| Command | Description |
|---|---|
/start |
Welcome message and help |
/status |
Show current session info |
/heartbeat |
Manually trigger a heartbeat check-in |
Connect to Letta Code
Any LettaBot agent can also be directly chatted with through Letta Code. Use the /status command to find your agent_id, and run:
letta --agent <agent_id>
Security
Network Architecture
LettaBot uses outbound connections only - no public URL or gateway required:
| Channel | Connection Type | Exposed Ports |
|---|---|---|
| Telegram | Long-polling (outbound HTTP) | None |
| Slack | Socket Mode (outbound WebSocket) | None |
| Discord | Gateway (outbound WebSocket) | None |
| Outbound WebSocket via Baileys | None | |
| Signal | Local daemon on 127.0.0.1 | None |
Tool Execution
By default, the agent is restricted to read-only operations:
Read,Glob,Grep- File explorationweb_search- Internet queriesconversation_search- Search past messages
Access Control
LettaBot supports pairing-based access control. When TELEGRAM_DM_POLICY=pairing:
- Unauthorized users get a pairing code
- You approve codes via
lettabot pairing approve telegram <CODE> - Approved users can then chat with the bot
Development
# Run in development mode (auto-reload)
npm run dev
# Build for production
npm run build
# Start production server
lettabot server
Troubleshooting
Session errors / "Bad MAC" messages These are normal Signal Protocol renegotiation messages. They're noisy but harmless.
Messages going to wrong chat Clear the session and re-link:
rm -rf ./data/whatsapp-session
lettabot server # Scan QR again
Signal
Port 8090 already in use
SIGNAL_HTTP_PORT=8091
General
Agent not responding Delete the agent store to create a fresh agent:
lettabot destroy
Documentation
Acknowledgement
Some skills were adapted from Moltbot.
License
Apache-2.0