Gateway Overview
One gateway process connecting Telegram, Discord, Slack, WhatsApp, Signal, and Email.
v0.20.5source on GitHub
The messaging gateway is a single process (synapse gateway) that connects every supported platform. Once running, many slash commands work identically across interfaces — your agent is reachable wherever you already are.
Supported platforms
- Telegram
- Discord
- Slack
- Signal
- + additional community adapters (iMessage via BlueBubbles, WeChat, QQ bot, and more) ship in the platforms directory
Setup
bash
synapse gateway setup # guided configuration per platform
synapse gateway start # start the gatewayThen message your bot from any configured platform. Pairing controls who can talk to it.
Platform notes
| Platform | Notes |
|---|---|
| Telegram | Bot token via BotFather; voice memos transcribed automatically |
| Discord | Bot application; works in servers and DMs |
| Slack | Socket-mode app; no public URL needed |
| Via bridge; scan to pair | |
| Signal | Via signal-cli; number-based pairing |
| IMAP/SMTP; good for longer, async tasks |
Shared slash commands
| Action | CLI | Messaging |
|---|---|---|
| Start fresh | /new · /reset | /new · /reset |
| Change model | /model [provider:model] | /model [provider:model] |
| Personality | /personality [name] | /personality [name] |
| Retry/undo | /retry · /undo | /retry · /undo |
| Context usage | /compress · /usage · /insights | /compress · /usage · /insights |
| Skills | /skills · /<skill-name> | /<skill-name> |
| Interrupt | Ctrl+C or new message | /stop or new message |
Running it for real
The gateway needs a host that stays up: a VPS, a home server, Docker, or Railway. On a laptop it stops when you close the lid — see Deployment for always-on options.