github/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-06-07 22:09:57 +00:00
Code Issues Packages Projects Releases Wiki Activity

revert(docs): undo markdownlint autofix churn

Browse Source
This commit is contained in:
Sebastian
2026-02-06 10:00:08 -05:00
parent c7aec0660e
commit 0a1f4f666a
83 changed files with 192 additions and 253 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/channels/telegram.md
View File

@@ -74,9 +74,9 @@ If both env and config are set, config takes precedence.
Multi-account support: use `channels.telegram.accounts` with per-account tokens and optional `name`. See [`gateway/configuration`](/gateway/configuration#telegramaccounts--discordaccounts--slackaccounts--signalaccounts--imessageaccounts) for the shared pattern.
1. Start the gateway. Telegram starts when a token is resolved (config first, env fallback).
2. DM access defaults to pairing. Approve the code when the bot is first contacted.
3. For groups: add the bot, decide privacy/admin behavior (below), then set `channels.telegram.groups` to control mention gating + allowlists.
3. Start the gateway. Telegram starts when a token is resolved (config first, env fallback).
4. DM access defaults to pairing. Approve the code when the bot is first contacted.
5. For groups: add the bot, decide privacy/admin behavior (below), then set `channels.telegram.groups` to control mention gating + allowlists.
## Token + privacy + permissions (Telegram side)
@@ -365,7 +365,6 @@ Alternate (official Bot API):
1. DM your bot.
2. Fetch updates with your bot token and read `message.from.id`:
```bash
curl "https://api.telegram.org/bot<bot_token>/getUpdates"
```