From cf2efbe5d515856ca901a48527ebadf827f74cc7 Mon Sep 17 00:00:00 2001 From: solodmd Date: Wed, 1 Jul 2026 17:33:24 +0800 Subject: [PATCH] docs(gateway): fix Telegram streaming default in config-channels.md (#98453) The config example in docs/gateway/config-channels.md incorrectly listed streaming default as "off". The actual runtime default is "partial", as confirmed by the Telegram plugin's default resolver. docs/channels/telegram.md already correctly documents the default as "partial". Co-authored-by: Claude --- docs/gateway/config-channels.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/gateway/config-channels.md b/docs/gateway/config-channels.md index 4ec9ff6e8d18..9330ed7c4112 100644 --- a/docs/gateway/config-channels.md +++ b/docs/gateway/config-channels.md @@ -203,7 +203,7 @@ WhatsApp runs through the gateway's web channel (Baileys Web). It starts automat historyLimit: 50, replyToMode: "first", // off | first | all | batched linkPreview: true, - streaming: "partial", // off | partial | block | progress (default: off; opt in explicitly to avoid preview-edit rate limits) + streaming: "partial", // off | partial | block | progress (default: partial) actions: { reactions: true, sendMessage: true }, reactionNotifications: "own", // off | own | all mediaMaxMb: 100,