openclaw - 💡(How to fix) Fix [Bug]: Delivery-mirror leaks messages across agents when multiple Telegram accounts bind to same peer [1 participants]

Summary

When multiple agents are bound to the same Telegram peer via different Telegram accounts (different bot tokens), the delivery-mirror mechanism incorrectly syncs outbound messages to all sessions bound to that peer, instead of only the session belonging to the agent that sent the message.

Environment

• OpenClaw version: 2026.4.15
• Platform: macOS (Darwin 25.4.0 arm64)
• Channel: Telegram
• Configuration: 4 agents (main, dev, money, operations) each bound to separate Telegram accounts (4 different bot tokens) but all to the same peer (DM with user 8267898996)

Configuration

{
  "bindings": [
    { "agentId": "main", "match": { "channel": "telegram", "accountId": "default" } },
    { "agentId": "dev", "match": { "channel": "telegram", "accountId": "dev" } },
    { "agentId": "money", "match": { "channel": "telegram", "accountId": "money" } },
    { "agentId": "operations", "match": { "channel": "telegram", "accountId": "operations" } }
  ],
  "channels": {
    "telegram": {
      "accounts": {
        "default": { "botToken": "8596451837:..." },
        "dev": { "botToken": "8638828395:..." },
        "money": { "botToken": "8708397593:..." },
        "operations": { "botToken": "8605344542:..." }
      }
    }
  },
  "session": { "dmScope": "per-channel-peer" }
}

Reproduction Steps

1. Configure multiple agents with separate Telegram accounts (different bot tokens)
2. All agents bound to the same peer (same user DM)
3. Send a message to one agent (e.g., via dev bot)
4. That agent sends a reply with media attachments
5. The delivery-mirror syncs the outbound message to multiple session transcripts

Expected Behavior

• Agent dev sends message → delivery-mirror syncs to agent:dev:telegram:direct:8267898996 session only
• Each agent's outbound messages should only appear in its own session transcript

Actual Behavior

From session transcript inspection:

main session (agent:main:telegram:direct:8267898996):

{"type":"message","id":"xxx","message":{"role":"assistant","content":[{"type":"text","text":"LingoTools.ipa"}],"model":"delivery-mirror"}}
{"type":"message","id":"xxx","message":{"role":"assistant","content":[{"type":"text","text":"lingostock_sim.png"}],"model":"delivery-mirror"}}
{"type":"message","id":"xxx","message":{"role":"assistant","content":[{"type":"text","text":"lingostock_home.png"}],"model":"delivery-mirror"}}

These delivery-mirror entries with "model":"delivery-mirror" are screenshots sent by dev agent, not main agent. They incorrectly appear in main's session transcript.

Root Cause Analysis

From sessions_list API response:

{
  "key": "agent:main:telegram:direct:8267898996",
  "deliveryContext": { "channel": "telegram", "to": "telegram:8267898996", "accountId": "default" }
}
{
  "key": "agent:dev:telegram:direct:8267898996",
  "deliveryContext": { "channel": "telegram", "to": "telegram:8267898996", "accountId": "dev" }
}

Both sessions have deliveryContext.to: "telegram:8267898996" without differentiating by accountId.

When the Gateway performs delivery-mirror sync:

1. Agent sends message → deliveryContext contains { channel: "telegram", to: "telegram:8267898996" }
2. Gateway syncs outbound message back to session transcript
3. Gateway finds sessions by deliveryContext.to → finds both main and dev sessions
4. Syncs to both sessions instead of only the originating agent's session

The bug: deliveryContext should include accountId to uniquely identify which agent/session sent the message. The current deliveryContext.to format telegram:peer_id is ambiguous when multiple agents bind to the same peer via different accounts.

Proposed Fix

1. Include accountId in deliveryContext: Change format from telegram:8267898996 to telegram:default:8267898996 or similar, including the accountId
2. Or: delivery-mirror should use the session's origin.accountId instead of just deliveryContext.to when determining which session to sync to
3. Or: Add explicit accountId field to deliveryContext alongside channel and to

Related Issues

• #69443: Subagent RPC callback routed to wrong session
• #63116: Delivery-mirror session token overflow
• #51628: Telegram delivery queue recovery duplicates delivery-mirror entries

Impact

• Users with multiple agents bound to the same peer experience session transcript contamination
• Makes debugging harder (wrong messages in transcript)
• May affect memory/corpus generation if delivery-mirror entries are included