Bug Description

Telegram dispatch crashes with TypeError: Cannot read properties of undefined (reading 'trim') when processing follow-up messages in group chats bound to a non-default agent. The first message in a session works correctly; subsequent messages in the same session crash.

Environment

• OpenClaw version: 2026.3.28 (f9b1079)
• Hosting: Hostinger VPS, Docker container
• Node.js: v25.7.0
• Channel: Telegram group chat
• Agent: Non-default agent with dedicated workspace and Telegram account binding

Reproduction Steps

1. Configure a secondary agent (e.g., pmm3-manager) with:

   • Own Telegram bot account
   • Group chat binding via bindings[]
   • groupChat.mentionPatterns for @mention detection
   • Sandbox mode: off (also reproduces with sandbox enabled)

2. Send a message mentioning the bot in the bound group → first response works

3. Reply to the bot's response in the same group → crash:

   [telegram] dispatch failed: TypeError: Cannot read properties of undefined (reading 'trim')

   User sees: "Something went wrong while processing your request. Please try again."

Error Location

From the file log, the error originates in dispatch-acp.runtime (compiled bundle). The crash is in:

function hashText(text) { return text.trim(); }

hashText is called with undefined — likely from a tool call result or session history entry where text is not set.

Agent Configuration (relevant parts)

{
  "id": "pmm3-manager",
  "name": "PMM3 Research Group Agent",
  "model": {
    "primary": "github-copilot/gpt-5-mini",
    "fallbacks": ["google/gemini-2.5-flash", "google/gemini-3-flash-preview"]
  },
  "workspace": "/data/.openclaw/workspace-pmm3",
  "sandbox": { "mode": "off" },
  "groupChat": {
    "mentionPatterns": ["ая", "айона", "aya", "ayona", "@ayona_pmm_bot"],
    "historyLimit": 20
  }
}

Binding:

{
  "agentId": "pmm3-manager",
  "match": {
    "channel": "telegram",
    "accountId": "pmm3-manager",
    "peer": { "kind": "group", "id": "-1003766168686" }
  }
}

Key Observations

• First message in a new session works (bot responds with tool calls like web_fetch, read)
• Follow-up message in the same session crashes
• Session store shows 0 messages after crash (messages not persisted)
• The crash occurs regardless of sandbox mode (tested with mode: "all" and mode: "off")
• Default agent (main) in DM does not exhibit this bug

Suggested Fix

Guard hashText against undefined input:

function hashText(text) { return (text ?? "").trim(); }

Or add a null check at the call site before invoking hashText.

Workaround

None found. Clearing sessions does not help since the crash occurs during dispatch before session persistence.