Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Bug: Non-default agents generate responses but Telegram delivery fails silently

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Fix Action

Workaround

Using the default agent (Alf/main) as a proxy: manually reading session files of affected agents and relaying responses via sessions_send to the user's direct chat.

Code Example

{
  "agents": {
    "list": [
      {"id": "main", "default": true},
      {"id": "mel", "workspace": "~/.openclaw/workspace-mel"},
      {"id": "french", "workspace": "~/.openclaw/workspace-french"}
    ]
  },
  "channels": {
    "telegram": {
      "groups": {
        "-1003993256051": {
          "topics": {
            "450": {"agentId": "mel"},
            "1218": {"agentId": "french"},
            "*": {"agentId": "main"}
          }
        }
      }
    }
  }
}
RAW_BUFFERClick to expand / collapse

Bug Description

After upgrading to v2026.5.20, non-default agents (configured in agents.list with id != "main") receive Telegram messages, generate responses, but the responses never get delivered to Telegram. The message stays in the agent's session file but sendMessage is never called.

Affected Agents

  • Mel (agentId: "mel") - Topic 450
  • French (agentId: "french") - Topic 1218

Evidence

Mel (Topic 450)

  • Messages arrive: [telegram] Inbound message telegram:group:-1003993256051:topic:450 -> @alf_aiagent_bot
  • Response generated in session file (confirmed via tail on .jsonl)
  • No sendMessage log entry for the response
  • User receives "Something went wrong" in Telegram

French (Topic 1218)

  • Messages arrive: [telegram] Inbound message telegram:group:-1003993256051:topic:1218 -> @alf_aiagent_bot
  • Response generated in session file (confirmed, e.g. "¡Qué tal, Andrés!")
  • No sendMessage log entry for the response
  • Response visible in nested agent logs (agent:nested) but never sent

Configuration

{
  "agents": {
    "list": [
      {"id": "main", "default": true},
      {"id": "mel", "workspace": "~/.openclaw/workspace-mel"},
      {"id": "french", "workspace": "~/.openclaw/workspace-french"}
    ]
  },
  "channels": {
    "telegram": {
      "groups": {
        "-1003993256051": {
          "topics": {
            "450": {"agentId": "mel"},
            "1218": {"agentId": "french"},
            "*": {"agentId": "main"}
          }
        }
      }
    }
  }
}

Environment

  • OpenClaw version: 2026.5.20
  • Previous version: 2026.5.19 (was working before upgrade)
  • OS: Ubuntu 24.04 (Linux 6.8.0-117-generic)
  • Node: v22.22.2
  • Installation: Global npm

Workaround

Using the default agent (Alf/main) as a proxy: manually reading session files of affected agents and relaying responses via sessions_send to the user's direct chat.

Related

This started immediately after openclaw update to v2026.5.20. The update process itself had issues (missing module inbound.runtime-BG8Hdxzs.js which required full reinstallation via npm install -g openclaw@latest).

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Bug: Non-default agents generate responses but Telegram delivery fails silently