openclaw - 💡(How to fix) Fix [Bug]: Possible Telegram account/group suspension after enabling bot-to-bot multi-bot setup

Bug type

Operational incident / Telegram enforcement risk

Summary

After enabling and testing a multi-bot / bot-to-bot Telegram setup with OpenClaw, several Telegram groups were suspended and the operator's Telegram account was also suspended.

I cannot prove causality from the local side yet, but the timing is close enough that this should be tracked as a possible production safety issue around Telegram Bot-to-Bot Communication Mode, multi-account OpenClaw deployments, and bot-loop/rate-limit behavior.

Why this matters

Existing related issues already discuss the technical risks:

• #79077: Telegram bot-to-bot / guest-bot support needs sender-type policy, peer mapping, loop guard, and doctor diagnostics.
• #79111: suspected Telegram allowFrom drift / auto-allowlist mutation after bot-to-bot inbound.
• #69165: outbound Telegram send queue and retry_after-aware backoff.
• #50866: previous Telegram 429 crash spiral from multiple agents/crons sending at once.

This report adds a more severe operator-side impact: Telegram enforcement may suspend groups or accounts if a bot-to-bot setup creates noisy behavior, loops, or traffic patterns that look abusive/spammy.

Observed impact

• Multiple Telegram groups were suspended after applying a multi-bot / bot-to-bot setup.
• The operator's Telegram account was also suspended.
• The timing happened after enabling or experimenting with bot-to-bot / multi-bot operation.
• No direct Telegram enforcement reason was available from OpenClaw logs at the time of reporting.

Expected behavior

OpenClaw should make Telegram bot-to-bot setups safe by default, or at minimum warn loudly before an operator enables a configuration that can trigger Telegram enforcement risk.

Safe behavior should likely include:

• default humans-only sender policy for Telegram;
• explicit peer-bot allowlist, separate from normal allowFrom;
• per-sender and per-peer rate limits;
• circuit breaker for repeated bot-to-bot exchanges;
• outbound Telegram queue / pacing by chat and topic;
• doctor warnings when Telegram bot IDs appear in allowFrom or groupAllowFrom;
• doctor warnings when multiple Telegram accounts can mutually respond to each other;
• clear logs when bot-originated updates are accepted, rejected, throttled, or suppressed;
• a documented "safe bot-to-bot setup" guide.

Actual behavior

Bot-to-bot / multi-bot setups can currently be configured in ways that are operationally risky:

• peer bot IDs can be treated similarly to normal allowed users;
• Telegram-specific bot-loop protection is not clearly enforced;
• outbound bursts can still be possible depending on deployment/version/config;
• operators may not get a strong warning that Telegram itself treats bot-to-bot loops as dangerous.

Reproduction status

Not yet deterministic.

This is an incident report based on a real operator observation. The exact enforcement trigger is unknown.

Useful reproduction direction:

1. Configure multiple OpenClaw Telegram accounts/bots.
2. Enable Telegram Bot-to-Bot Communication Mode via BotFather.
3. Put the bots into the same groups/workspace.
4. Configure mutual or semi-mutual bot access through allowFrom / groupAllowFrom or any equivalent peer path.
5. Trigger bot-to-bot replies or delegation.
6. Observe whether message loops, bursts, 429s, config drift, or Telegram enforcement actions occur.

Suggested immediate mitigation

Until Telegram-specific bot-to-bot safeguards land:

• do not put bot IDs into normal allowFrom/groupAllowFrom in both directions;
• avoid mutual bot-to-bot reply loops;
• use one-way delegation only;
• keep Bot-to-Bot mode disabled unless explicitly testing;
• add local watchdogs for outbound message volume and allowlist drift;
• keep per-chat outbound pacing conservative;
• document this risk near the Telegram bot-to-bot feature request.

Environment

Exact version/config can be filled in later by the reporter if needed.

Known context:

• Channel: Telegram
• Setup type: OpenClaw multi-account / multi-bot
• Feature involved: Telegram Bot-to-Bot Communication / multi-bot operation
• Impact: group suspension and operator account suspension

Related

• #79077
• #79111
• #69165
• #50866