telegram-agent-routerlisted

# Telegram Agent Router — Multi-Agent Architecture > **Core thesis**: A Telegram bot is not a chatbot. It is a routing layer > over a team of specialists, backed by a PostgreSQL state machine. > Every message is a dispatch decision. Every conversation is a session. > Every session has memory. This skill documents the architecture, patterns, and production code for building Telegram bots that coordinate multiple specialized AI agents with PostgreSQL-native state, intent-based routing, and persistent cross-session memory. **Targets production multi-agent Telegram deployments with durable PostgreSQL state.** --- ## ARCHITECTURE OVERVIEW ``` User │ ▼ HTTPS (Telegram sends to your endpoint) ┌────────────────────────────────────────────┐ │ WEBHOOK RECEIVER │ │ /telegram/webhook │ │ Validates token · Deduplicates · Queues │ └──────────────┬─────────────────────────────┘ │ ▼ ┌────────────────────────────────────────────┐ │ INTENT CLASSIFIER │ │ command → direct dispatch │ │ free text → LLM classification │ │ ambiguous → confidence check │ └──────────────┬─────────────────────────────┘ │ ▼ ┌────────────────────────────────────────────┐ │ ROUTER │ │ Loads session state from PostgreSQL │ │ Selects target agent │ │ Injects memory context