openclaw - 💡(How to fix) Fix feat: Telegram Guest Mode (来宾模式) for single-bot personal use (Bot API 10.0)

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Code Example

{
  channels: {
    telegram: {
      guestMode: {
        enabled: true,
        // Reuse existing allowFrom / groupAllowFrom for access control
      }
    }
  }
}
RAW_BUFFERClick to expand / collapse

Feature Request: Telegram Guest Mode Support

Telegram Bot API 10.0 (May 8, 2026) introduced Guest Mode — bots can be @-mentioned in any group chat without being a member. The bot receives only the message it was mentioned in and can reply via answerGuestQuery.

This is especially useful for personal/single-bot setups where:

  • The bot owner does NOT want to add the bot as a group member
  • The bot should only respond when @-mentioned by the owner
  • No need for multi-bot routing or bot-to-bot communication

Use Case

A single-user OpenClaw bot (one Telegram account, one agent) that the owner can @-mention in various groups without adding it. The bot should:

  1. Receive guest messages when @-mentioned in a group (via guest_message update)
  2. Reply via answerGuestQuery
  3. Respect existing access control (allowFrom, groupAllowFrom) even in guest mode
  4. Not read the broader group history (this is by Telegram design)

Current Gap

LayerStatus
grammY (underlying lib, v1.43.0)✅ Type defs for guest_message, guest_query_id, answerGuestQuery exist
OpenClaw Telegram ingress handler❌ Does not process guest_message updates; only handles regular message updates
OpenClaw delivery❌ No answerGuestQuery support for guest replies

Config Suggestion

A simple config toggle would suffice for personal/single-bot setups:

{
  channels: {
    telegram: {
      guestMode: {
        enabled: true,
        // Reuse existing allowFrom / groupAllowFrom for access control
      }
    }
  }
}

Related

Environment

  • OpenClaw version: 2026.5.28
  • grammY version: 1.43.0 (already has guest types)
  • Bot Father: Guest Mode enabled on the bot

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix feat: Telegram Guest Mode (来宾模式) for single-bot personal use (Bot API 10.0)