Skip to main content

​
Telegram

This is a shipped runtime-backed surface: direct sends are implemented, the serve loop is implemented, and the channel can join multi-channel-serve or gateway run.

​
At A Glance

FieldValue
Catalog idtelegram
Config keytelegram
Implementation statusruntime_backed
Transporttelegram_bot_api_polling
Aliasesnone
Default send target kindconversation

​
Minimal Config

[telegram]
enabled = true
bot_token_env = "TELEGRAM_BOT_TOKEN"
allowed_chat_ids = [123456789]

​
Smoke Test

loong telegram-send --target "123456789" --text "hello from loong"
loong telegram-serve

​
Command Surface

OperationCommandUsage or status
direct sendtelegram-sendUsage: loong telegram-send [OPTIONS] —target <TARGET> —text <TEXT>
reply looptelegram-serveUsage: loong telegram-serve [OPTIONS]

​
Required Fields For Send

RequirementConfig pathsEnv pointer pathsDefault env
channel enabledtelegram.enabled
telegram.accounts.<account>.enabled		nonenone
bot tokentelegram.bot_token
telegram.accounts.<account>.bot_token		telegram.bot_token_env
telegram.accounts.<account>.bot_token_env		TELEGRAM_BOT_TOKEN

​
Required Fields For Serve

RequirementConfig pathsEnv pointer pathsDefault env
channel enabledtelegram.enabled
telegram.accounts.<account>.enabled		nonenone
bot tokentelegram.bot_token
telegram.accounts.<account>.bot_token		telegram.bot_token_env
telegram.accounts.<account>.bot_token_env		TELEGRAM_BOT_TOKEN
allowed chat idstelegram.allowed_chat_ids
telegram.accounts.<account>.allowed_chat_ids		nonenone

​
Gateway And Ownership

This surface can run directly through its own *-serve command, or under Gateway And Supervision through multi-channel-serve and gateway run.

​
Operator Notes

  • Telegram remains the smallest runtime-backed reply-loop path. Keep allowed_chat_ids tight and explicit.