openclaw/extensions/telegram
Robin Waslander 3847ace25b
fix(telegram): preserve forum topic routing for /new and /reset (#56654)
Build a topic-qualified routing target (telegram:<chatId>:topic:<threadId>)
for native commands in forum groups so /new and /reset stay scoped to
the active topic instead of falling back to General.

General topic (threadId=1) correctly falls through to the base chat
target since Telegram rejects message_thread_id=1 on sends.

Add regression tests for topic routing and General topic edge case.

Fixes #35963
2026-03-29 00:21:41 +01:00
..
src fix(telegram): preserve forum topic routing for /new and /reset (#56654) 2026-03-29 00:21:41 +01:00
allow-from.ts perf: split telegram audit runtime seams 2026-03-22 00:53:12 +00:00
api.ts refactor: route more test seams through public plugin APIs 2026-03-27 13:46:17 +00:00
channel-config-api.ts refactor: move channel config metadata into plugin-owned manifests 2026-03-27 01:59:30 +00:00
index.ts refactor: clean extension api boundaries 2026-03-17 09:38:21 -07:00
openclaw.plugin.json chore: Run `pnpm format:fix`. 2026-01-31 21:13:13 +09:00
package-manifest.contract.test.ts refactor: move extension-owned tests to extensions 2026-03-27 21:37:09 +00:00
package.json chore: prepare 2026.3.28-beta.1 release 2026-03-28 22:24:51 +00:00
runtime-api.ts refactor: move provider seams behind plugin sdk surfaces 2026-03-27 23:26:26 +00:00
setup-entry.ts refactor: clean extension api boundaries 2026-03-17 09:38:21 -07:00
test-api.ts refactor: route plugin runtime through bundled seams 2026-03-27 16:40:27 +00:00
update-offset-runtime-api.ts refactor: remove remaining core extension reach-ins 2026-03-27 13:46:16 +00:00