#Thanks @Kaspre i will try to make a

1 messages · Page 1 of 1 (latest)

blissful kindle
#

Moving to a thread so we don't clutter up the main channel. I had my agent do a quick analysis. Let me know if this is an accurate summary.

#

Hey @ruby belfry — dug into your list while you write up the proper post. A few things to flag:

1. PR #2731 is the opposite direction. It fixes spurious topic splits in non-forum groups (regular reply chains getting their own session keys). Merged Jan 28, in stable since v2026.1.29. Not a session-bleed fix.

2. All 4 issues you listed are closed, not open:

  • #17980 → fixed by commit e20b87f1b (Feb 16)
  • #19144 → superseded by #19213, confirmed working in 2026.2.19
  • #18168 → marked resolved by #17980
  • #14762 → auto-closed stale Mar 18, consolidated to #15787 (also auto-closed stale)

3. Inbound session-keying is verified fixed in current main. clawsweeper's #79005 closing comment cited source paths + a regression test showing forum messages route to agent:main:telegram:group:<id>:topic:<thread>. Shipped
v2026.1.29.

Where it's still rough — outbound delivery to topics (the #14762 territory). Cluster of fixes landed in stable v2026.5.7 (May 7):

  • #72317 preserve cron topic delivery after timeout
  • #76764 fix forum topic final delivery
  • #76049 command topic session files
  • #76719 scoped topic channelId for embedded recall

In current 5.10 betas (not stable yet): #78575, #79700, #76951.

Your "BOT API + Channel Mapping" workaround reads outbound to me, not inbound — agent sending to the wrong topic vs. arriving and bleeding into one session. Worth pinning down which.

For the proper post, three things would make it actionable:

  1. Exact version (openclaw --version + channel). Older than v2026.5.7? Half the cluster above isn't in your build.
  2. Direction — wrong topic on outbound, or merged sessions on inbound?
  3. Fresh repro on latest stable. The 4 old issues are closed; the barnacle bot's last word was "open a new issue on latest with fresh repro." Thread-necro won't move; a clean new issue will.
ruby belfry
#

hey - i just tested it after updating to the latest beta. here a potential bugreport:

[5.10-beta.5] Telegram Supergroup Forum Topics — Inbound Messages Not Processed

Summary

After updating from v2026.5.7 to v2026.5.10-beta.5 (1ba6893), the bot fails to process inbound messages from Telegram Supergroup Forum Topics. The "typing..." indicator appears, but no response is generated. Outbound messages work correctly.

Environment

Component Version/Setting
OpenClaw v2026.5.10-beta.5 (1ba6893)
Previous v2026.5.7 (same issue present)
Model ollama/kimi-k2.6:cloud
OS Ubuntu 22.04 LTS
Node v24.14.0

Configuration
{
"telegram": {
"enabled": true,
"dmPolicy": "allowlist",
"botToken": {
"source": "env",
"id": "TELEGRAM_BOT_TOKEN"
},
"allowFrom": [6664056209],
"groups": {
"-1003859824887": {
"requireMention": false,
"topics": {
"1": { "requireMention": false }
}
}
},
"groupPolicy": "allowlist",
"streaming": { "mode": "partial" }
}
}

Steps to Reproduce

  1. Update OpenClaw from v2026.5.7 to v2026.5.10-beta.5
  2. Configure Telegram Supergroup with Forum Topics (see config above)
  3. Send message to Topic #1 (General) in Supergroup "KI-Chat X"
  4. Observe "Kaito typing..." appears briefly
  5. Result No response generated, no session update, no logs

Expected Behavior

• Inbound message creates/updates session: agent:main:telegram:group:-1003859824887:topic:1
• Bot generates response in the same topic

#

Actual Behavior

Test Case Method Result
Message without mention Direct text in #general ❌ Not processed
Message with @mention "@kaito_moltbot test" ❌ Not processed
Outbound test message tool to group ✅ Works — lands in correct topic
Direct chat Private message to bot ✅ Works

Debug Information

  1. Session Status
    $ sessions_list --active 5min
    → Only Direct-Chat session visible
    → No Supergroup session created/updated

  2. Command Logs
    $ tail -5 ~/.openclaw/logs/commands.log
    2026-05-12T15:23:45 → agent:main:telegram:group:-1003859824887:topic:1 (first message)
    [No new entries for subsequent messages]

  3. Telegram API Status
    $ curl "https://api.telegram.org/bot$TOKEN/getChatMember?chat_id=-1003859824887&user_id=8493334521"
    → Status: "administrator"
    → can_manage_topics: true
    → All permissions granted

  4. Webhook/Polling Check
    $ curl "https://api.telegram.org/bot$TOKEN/getWebhookInfo"
    → "url": "" (empty — using polling mode)
    → "pending_update_count": 0

  5. Manual API Test
    $ curl "https://api.telegram.org/bot$TOKEN/getUpdates?limit=10"
    → No updates visible for Supergroup messages

#

Hypotheses Tested

Hypothesis Tested Result
Wrong Chat ID URL vs Config comparison ❌ ID is correct (-1003859824887)
Permission issue getChatMember check ❌ Bot is Admin with all rights
requireMention filter Tested with @mention ❌ Still not processed
Config corruption Fresh config validation ❌ Config is valid
Outbound routing message tool test ❌ Outbound works

rmission issue | getChatMember check | ❌ Bot is Admin with all rights |
| requireMention filter | Tested with @mention | ❌ Still not processed |
| Config corruption | Fresh config validation | ❌ Config is valid |
| Outbound routing | message tool test | ❌ Outbound works fine |

Related Issues (from Discord analysis by Kaspre)

• #17980 → fixed by commit e20b87f1b (Feb 16)
• #19144 → superseded by #19213, confirmed in v2026.2.19
• #18168 → resolved by #17980
• #14762 → auto-closed, consolidated to #15787

Note: All 4 issues above are closed. This appears to be a new or different regression.

Key Findings

  1. Outbound delivery works — Bot can send messages to correct forum topic
  2. Inbound processing fails — Messages from Supergroup Topics not received
  3. Direct Chat unaffected — Private messages work normally
  4. No error logs — Silent failure, no crash or error
  5. "typing..." appears — Bot is online and connected, but doesn't receive message

Possible Root Causes

  1. Polling offset issue — getUpdates offset skips Supergroup messages
  2. Update filter — Polling excludes forum_topic or supergroup updates
  3. Session routing — Inbound messages not routed to correct session key
  4. Regression in beta — New change in 5.10-beta affecting topic handling
#

Request

Please investigate why inbound messages from Telegram Supergroup Forum Topics are silently dropped in v2026.5.10-beta.5, despite correct configuration and permissions.

───

Labels: bug, telegram, forum-topics, supergroup, inbound
Priority: High — Breaks primary use case for group collaboration

ruby belfry
#

hey @blissful kindle is this good enough for a issue post - or how should i proceed. Sorry to bother you 🙁

blissful kindle
#

Yeah, seems good. Once the issue is open, contributors can ask more questions if they have any, and I'm sure someone will jump on this. One of the maintainers has a telegram focus, so if you mention there's an open issue relating to Telegram, they may want to give it some attention. Of course, you could also try the users-helping-users channel; if it is just a misconfiguration rather than a bug, that would be a better and faster way to get help.