OpenAgno follows the interface surface currently exposed by Agno: WhatsApp, Slack, Telegram, AG-UI, and A2A. TheDocumentation Index
Fetch the complete documentation index at: https://docs.openagno.com/llms.txt
Use this file to discover all available pages before exploring further.
ai_sdk channel is not part of the supported runtime path and should not be used in new configurations.
English
Quick matrix
| Channel or protocol | Activation | Requirements |
|---|---|---|
| WhatsApp Cloud API | channels: [whatsapp] + whatsapp.mode: cloud_api | Meta credentials |
| WhatsApp QR | channels: [whatsapp] + whatsapp.mode: qr_link | Optional Node bridge |
| Slack | channels: [slack] | SLACK_TOKEN, SLACK_SIGNING_SECRET |
| Telegram | channels: [telegram] | TELEGRAM_TOKEN |
| AG-UI | channels: [agui] | extra .[protocols] |
| A2A | a2a.enabled: true | extra .[protocols] |
WhatsApp Cloud API
GET /whatsapp/webhookPOST /whatsapp/webhook
Local development without a domain
During local development you usually need a public tunnel for WhatsApp, Slack, or Telegram webhooks. In OpenAgno, the practical setup is documented in /whatsapp-tunnel. For controlled development without a real signature:WhatsApp QR
Slack
Telegram
AG-UI and A2A
Español
OpenAgno sigue la superficie de interfaces expuesta por Agno en el runtime actual: WhatsApp, Slack, Telegram, AG-UI y A2A. El canalai_sdk no forma parte de la ruta compatible vigente y no debe usarse en nuevas configuraciones.
Compatibilidad
slackytelegramforman parte de las dependencias base.aguiya2arequieren instalar extras.ai_sdkno forma parte del runtime compatible actual de OpenAgno.