The default. Send an email, get a response. Works from any device. Learn more →
Interfaces
Your agent supports multiple interfaces. Same agent, same memory — different ways to communicate.
Telegram
Chat with your agent on Telegram. Create a bot, connect it, go. Learn more →
Slack
Chat in your Slack workspace. @mention to wake your agent. Learn more →
Comparison
Section titled “Comparison”| Feature | Telegram | Slack | |
|---|---|---|---|
| Setup | None | Bot token | Bot token + signing secret |
| Response | 10-30s | Instant ack, then reply | 👀 ack, then reply |
| Mobile | Native email | Telegram app | Slack app |
| Threading | Email threads | Chat | Slack threads |
| Attachments | ✓ | ✓ | ✓ |
| Commands | ✓ | ✓ | ✓ |
Shared state
Section titled “Shared state”All interfaces share the same:
- Storage —
/datadirectory in R2 - Memory —
MEMORY.mdfile - Sessions — Conversation history
Start a conversation via email, continue on Telegram — the context carries over.
Commands work everywhere
Section titled “Commands work everywhere”| Command | Effect |
|---|---|
/clear | Start fresh session |
/resume | List recent sessions |
/resume abc1 | Resume specific session |
/compact | Compress context |
/model haiku | Switch to Haiku |
/model sonnet | Switch to Sonnet |
/model opus | Switch to Opus |
Choosing an interface
Section titled “Choosing an interface”Use email when:
- You want async communication
- You’re on mobile without other apps
- You need email threading/archival
- You want to send attachments
Use Telegram when:
- You want quick back-and-forth
- You’re on mobile
- You want instant ack feedback
Use Slack when:
- You want team visibility
- You’re already in Slack for work
- You want threaded conversations