2.5 KiB
CLI Tools
LettaBot ships with a few small CLIs that the agent can invoke via Bash, or you can run manually. They use the same config/credentials as the bot server.
lettabot config
Manage your lettabot.yaml configuration.
lettabot config # Show current config summary + menu
lettabot config tui # Interactive core config editor
lettabot config encode # Encode config as base64 (for cloud deploy)
lettabot config decode <base64> # Decode base64 config back to YAML
Interactive TUI editor
lettabot config tui opens an interactive editor for the most common settings:
- Server auth -- switch between API/Docker mode, set API key or base URL
- Agent identity -- change agent name and ID
- Channels -- enable/disable channels and run their setup wizards
- Features -- toggle cron, heartbeat (with interval), and memfs
The TUI loads your existing config, lets you edit fields interactively, shows a summary of changes, and saves back to the same file. Non-core fields (providers, attachments, secondary agents, etc.) are preserved through the round-trip.
From the lettabot config menu, you can also choose "Open TUI editor" or "Edit config file" to open the raw YAML in your $EDITOR.
lettabot-message
Send a message to the most recent chat, or target a specific channel/chat.
lettabot-message send --text "Hello from a background task"
lettabot-message send --text "Hello" --channel slack --chat C123456
lettabot-message send --file /tmp/report.pdf --text "Report attached" --channel discord --chat 123456789
lettabot-message send --file /tmp/voice.ogg --voice # Send as native voice note (see voice.md)
lettabot-react
Add a reaction to a message (emoji can be unicode or :alias:).
lettabot-react add --emoji :eyes: --channel discord --chat 123 --message 456
lettabot-react add --emoji "👍"
lettabot-history
Fetch recent messages from supported channels (Discord, Slack).
lettabot-history fetch --limit 25 --channel discord --chat 123456789
lettabot-history fetch --limit 10 --channel slack --chat C123456 --before 1712345678.000100
Notes:
- History fetch is not supported by the Telegram Bot API, Signal, or WhatsApp.
- If you omit
--channelor--chat, the CLI falls back to the last message target stored inlettabot-agent.json. - You need the channel-specific bot token set (
DISCORD_BOT_TOKENorSLACK_BOT_TOKEN). - File sending uses the API server and requires
LETTABOT_API_KEY(supported: telegram, slack, discord, whatsapp).