vercel / vercel/chat

Telegram: support guest mode (guest_message updates and answerGuestQuery)

Open
#871 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
2.4k
Forks
314
Avg merge
1d 18h
Merged PRs (30d)
63

Description

Bot API 10.0 (May 2026) added guest mode: users can @-mention a bot in chats it is not a member of. The update arrives as the new guest_message field on Update, with guest_bot_caller_user, guest_bot_caller_chat and guest_query_id on the message, and replies must go through the new answerGuestQuery method (returning SentGuestMessage) — sendMessage does not work for these.

The Telegram adapter's processUpdate currently only inspects message / edited_message / channel_post / edited_channel_post / callback_query / message_reaction, so guest updates are dropped silently and the bot appears unresponsive to guest callers.

Needed:

  • parse update.guest_message and dispatch it with the guest context attached (a mention-like event seems natural, since guest calls are always @-mentions)
  • a reply path using answerGuestQuery with the guest_query_id
  • a docs note that existing webhooks may need guest_message in allowed_updates

Refs: Bot API changelog, Telegram announcement

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the Telegram adapter's processUpdate entry point and trace the existing message, callback, and reaction dispatch paths. Add guest_message handling with guest context, a reply path using answerGuestQuery and guest_query_id, and a documentation note covering allowed_updates; done means guest mentions are dispatched and answered correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, documentation
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
56/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.