Bug type

Behavior bug (incorrect output/state without crash)

Summary

agent:main:main session sends responses to Telegram DMs even though only the telegram session should respond. Every message gets two replies.

Steps to reproduce

1. Set up Telegram channel with dmPolicy: pairing
2. Send any DM to the bot
3. Both agent:main:main and agent:main:telegram:direct:[id] respond to the same message

Expected behavior

Only agent:main:telegram:direct session responds to Telegram DMs. agent:main:main should stay silent.

Actual behavior

Both agent:main:main and agent:main:telegram:direct respond to every Telegram DM. User receives two replies per message.

OpenClaw version

2026.3.7

Operating system

macOS 26.3.1 (arm64)

Install method

npm global

Logs, screenshots, and evidence

Sessions JSON shows two active sessions responding to same Telegram DM:
- agent:main:telegram:direct:7463849194 (model: claude-sonnet-4-5, has deliveryContext)
- agent:main:main (model: claude-sonnet-4-5, no deliveryContext, no lastTo)

Both sessions send replies to Telegram on every incoming DM.
openclaw status shows: "default main active just now" alongside telegram session.

Impact and severity

Affected: Telegram DM users
Severity: High (duplicate responses on every message)
Frequency: 100% repro
Consequence: Confusing UX, agent persona conflict, extra API cost

Additional information

Affected: Telegram DM users
Severity: High (duplicate responses on every message)
Frequency: 100% repro
Consequence: Confusing UX, agent persona conflict, extra API cost