**CRITICAL: Cross-Agent Session Leakage with Separate Telegram Bots**
I have configured separate Telegram bots for different agents (
Issue:
- I sent a message to the
- The
- It seems OpenClaw is routing messages based on my Telegram
Impact:
- Unable to communicate with specific agents reliably.
- Agents "steal" messages intended for others solely because they were active recently.
- Strict channel-to-agent binding is failing or being overridden by session stickiness.
Config Context:
- Multiple
- Agents mapped to specific channels (presumably).
- User ID is the same across bots.
How can I enforce strict routing where messages to Bot A always go to Agent A, regardless of Agent B's activity?
hachadIssue:
- I sent a message to the
chad- The
ha- It seems OpenClaw is routing messages based on my Telegram
user_idhaImpact:
- Unable to communicate with specific agents reliably.
- Agents "steal" messages intended for others solely because they were active recently.
- Strict channel-to-agent binding is failing or being overridden by session stickiness.
Config Context:
- Multiple
telegram- Agents mapped to specific channels (presumably).
- User ID is the same across bots.
How can I enforce strict routing where messages to Bot A always go to Agent A, regardless of Agent B's activity?
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
83,815Members
Resources
Similar Threads
Was this page helpful?
