From 3c354c0907a6a7cd1d63721f15d937a921a5da3a Mon Sep 17 00:00:00 2001 From: Ayaan Zaidi Date: Mon, 20 Apr 2026 09:56:50 +0530 Subject: [PATCH] docs(telegram): clarify allowFrom setup ids --- docs/channels/telegram.md | 2 +- docs/help/faq.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/channels/telegram.md b/docs/channels/telegram.md index f7ade62ae5a..b39a0b6b909 100644 --- a/docs/channels/telegram.md +++ b/docs/channels/telegram.md @@ -115,7 +115,7 @@ Token resolution order is account-aware. In practice, config values win over env `channels.telegram.allowFrom` accepts numeric Telegram user IDs. `telegram:` / `tg:` prefixes are accepted and normalized. `dmPolicy: "allowlist"` with empty `allowFrom` blocks all DMs and is rejected by config validation. - Onboarding accepts `@username` input and resolves it to numeric IDs. + Setup asks for numeric user IDs only. If you upgraded and your config contains `@username` allowlist entries, run `openclaw doctor --fix` to resolve them (best-effort; requires a Telegram bot token). If you previously relied on pairing-store allowlist files, `openclaw doctor --fix` can recover entries into `channels.telegram.allowFrom` in allowlist flows (for example when `dmPolicy: "allowlist"` has no explicit IDs yet). diff --git a/docs/help/faq.md b/docs/help/faq.md index a5c51c5a9b3..4c1ebfb5033 100644 --- a/docs/help/faq.md +++ b/docs/help/faq.md @@ -767,7 +767,7 @@ for usage/billing and raise limits as needed. `channels.telegram.allowFrom` is **the human sender's Telegram user ID** (numeric). It is not the bot username. - Onboarding accepts `@username` input and resolves it to a numeric ID, but OpenClaw authorization uses numeric IDs only. + Setup asks for numeric user IDs only. If you already have legacy `@username` entries in config, `openclaw doctor --fix` can try to resolve them. Safer (no third-party bot):