vultr/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-05-06 20:20:42 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix(telegram): stabilize topic dispatch runtime

Browse Source
This commit is contained in:
Peter Steinberger
2026-05-04 08:25:02 +01:00
parent 48e1256810
commit 585ce38015
14 changed files with 216 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/channels/telegram.md
View File

@@ -777,11 +777,12 @@ curl "https://api.telegram.org/bot<bot_token>/getUpdates"
- `channels.telegram.dms["<user_id>"].historyLimit`
- `channels.telegram.retry` config applies to Telegram send helpers (CLI/tools/actions) for recoverable outbound API errors. Inbound final-reply delivery also uses a bounded safe-send retry for Telegram pre-connect failures, but it does not retry ambiguous post-send network envelopes that could duplicate visible messages.
CLI send target can be numeric chat ID or username:
CLI and message-tool send targets can be numeric chat ID, username, or a forum topic target:
```bash
openclaw message send --channel telegram --target 123456789 --message "hi"
openclaw message send --channel telegram --target @name --message "hi"
openclaw message send --channel telegram --target -1001234567890:topic:42 --message "hi topic"
```
Telegram polls use `openclaw message poll` and support forum topics:

2
docs/cli/message.md
View File

@@ -27,7 +27,7 @@ Channel selection:
Target formats (`--target`):
- WhatsApp: E.164, group JID, or WhatsApp Channel/Newsletter JID (`...@newsletter`)
- Telegram: chat id or `@username`
- Telegram: chat id, `@username`, or forum topic target (`-1001234567890:topic:42`, or `--thread-id 42`)
- Discord: `channel:<id>` or `user:<id>` (or `<@id>` mention; raw numeric ids are treated as channels)
- Google Chat: `spaces/<spaceId>` or `users/<userId>`
- Slack: `channel:<id>` or `user:<id>` (raw channel id is accepted)