Bug type

Regression (worked before, now fails)

Summary

Telegram streaming messages disappear when pinned main DM recipient mechanism is active

Steps to reproduce

1. Configure Telegram with streaming enabled:

"telegram": {
  "streaming": "progress",
  "dmPolicy": "open", 
  "allowFrom": ["*"]
}

2. Send a message to trigger streaming response
3. Observe streaming updates disappear or fail to persist

Expected behavior

Streaming messages should update correctly and persist as final messages

Actual behavior

Streaming messages disappear when pinned main DM recipient mechanism interferes with message routing

OpenClaw version

2026.3.x

Operating system

All platforms

Install method

All methods

Logs, screenshots, and evidence

No specific error logs - issue manifests as message disappearance

Impact and severity

• Affected: Users with Telegram streaming enabled and pinned mechanism active
• Severity: Medium (streaming feature becomes unreliable)
• Frequency: 100% reproducible with specific configuration
• Consequence: Streaming functionality is effectively broken

Additional information

Root cause analysis:
The conflict occurs because:

1. Streaming relies on continuous message edits for live preview
2. Pinned main DM recipient mechanism prevents certain routing updates for non-owner messages
3. This creates a conflict where streaming updates are blocked

Workaround:
Disable streaming in Telegram configuration:

"telegram": {
  "streaming": "off"
}

Proposed solutions:

1. Decouple streaming message handling from pinned recipient checks
2. Add configuration option to allow streaming to bypass pinned restrictions
3. Modify pinned logic to recognize streaming updates as special cases

This appears to be an architectural conflict between security mechanisms (pinned recipients) and user experience features (streaming).