Chat Gateways
Arcana can run as an assistant inside Telegram, Discord, Slack, and WhatsApp. Each adapter keeps its own chat/session context while using the same Arcana runtime underneath.
arcana gateway
The current gateway reference requires an active Pro or Enterprise license and recommends completing arcana console login first.
Supported platforms
| Platform | Primary restriction |
|---|---|
| Telegram | allowedUsers |
| Discord | allowedChannels |
| Slack | allowedChannels |
allowedUsers |
Configuration
{
"provider": "openai",
"model": "gpt-4o",
"gateway": {
"telegram": { "token": "111:xxx", "allowedUsers": ["12345678"] },
"discord": { "token": "xxx", "allowedChannels": ["987654321"] },
"slack": { "botToken": "xoxb-xxx", "signingSecret": "xxx", "allowedChannels": ["C0123ABC"] },
"whatsapp": { "phoneNumberId": "123456", "accessToken": "xxx", "appSecret": "xxx", "allowedUsers": ["14155551234"] }
}
}
Security
Allowlists are the default boundary. The existing gateway implementation refuses to start with a missing or empty allowlist unless the explicit local-development override is used. Do not expose gateway credentials or open chat access broadly in production.
Full gateway reference
Platform-specific setup steps, webhook details, limits, and troubleshooting remain in the Gateway reference.