From 22ea87d857d9e6f9fd5b3092362fcc438f71e5aa Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Sat, 25 Apr 2026 07:26:13 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@e8191e5b8f65f0e0544182e5ce193e096aa3354c --- .openclaw-sync/source.json | 4 ++-- docs/channels/telegram.md | 3 +++ 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index 04cc7d107..098f38879 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "a44800e929f742ca72d068e5ff3bd2a8eac2b71b", - "syncedAt": "2026-04-25T07:19:41.627Z" + "sha": "e8191e5b8f65f0e0544182e5ce193e096aa3354c", + "syncedAt": "2026-04-25T07:25:05.881Z" } diff --git a/docs/channels/telegram.md b/docs/channels/telegram.md index 50c0d1bc7..a787e3a82 100644 --- a/docs/channels/telegram.md +++ b/docs/channels/telegram.md @@ -704,6 +704,9 @@ curl "https://api.telegram.org/bot/getUpdates" The local listener binds to `127.0.0.1:8787`. For public ingress, either put a reverse proxy in front of the local port or set `webhookHost: "0.0.0.0"` intentionally. + Webhook mode validates request guards, the Telegram secret token, and the JSON body before returning `200` to Telegram. + OpenClaw then processes the update asynchronously through the same per-chat/per-topic bot lanes used by long polling, so slow agent turns do not hold Telegram's delivery ACK. +