openclaw - 💡(How to fix) Fix Telegram: add config toggle to disable supplemental conversation context window in DMs [1 comments, 2 participants]

Summary

The conversation context window feature introduced in 5.12 ("Telegram: render cached reply targets and nearby group chatter as one selected conversation context window") is useful for group chats but causes unnecessary token burn in direct messages.

In DMs, the full conversation history is already maintained in the session transcript. The supplemental context window adds the last 10 messages as a redundant Conversation context (untrusted, chronological, selected for current message) block on top of every user message, effectively doubling the context for recent messages.

Current Behavior

• recentLimit: 10 is hardcoded in bot-DVHbpZjZ.js line 2378
• Context is injected into every DM message regardless of config
• dmHistoryLimit: 0 does NOT disable this (controls session history replay, not supplemental context)
• contextVisibility only filters in group chats (isGroup check in shouldIncludeGroupSupplementalContext)

Expected Behavior

A config option to disable the supplemental conversation context window for DMs, e.g.:

{
  channels: {
    telegram: {
      dmConversationContext: false,  // or dmContextWindow: 0
    }
  }
}

Or respect dmHistoryLimit: 0 to also disable the supplemental context.

Environment

• OpenClaw 2026.5.12
• Telegram channel, direct messages
• Rolled back to 5.7 (last version without this feature)

Workaround

Use OpenClaw 2026.5.7 which does not have the conversation context window feature.