docs(telegram): document Bot API 10.0 guest mode media delivery - #298
Open
hashbender wants to merge 1 commit into
Open
docs(telegram): document Bot API 10.0 guest mode media delivery#298hashbender wants to merge 1 commit into
hashbender wants to merge 1 commit into
Conversation
|
Review Complete Risk: 🟢 Low (0/100) — no findings · 26 LOC across 1 file Documentation-only change to Telegram messaging guide. No code changes detected. Files Reviewed (1 files) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
guest_message/answerGuestQueryreply flow (Bot API 10.0) added by feat(telegram): two-phase guest reply — immediate stub + progressive streaming NousResearch/hermes-agent#51886 and feat(telegram): guest-mode native media delivery + lazy two-phase stub NousResearch/hermes-agent#52639: the two-phase stub → edit behavior, and the deliver-token media button flow for files that can't be attached directly to a guest reply.TELEGRAM_HOME_CHANNELconfig docs (staging chat required for cached-file delivery) and the documented limitations (10-minute delivery-token TTL, no session stickiness across guest turns).Why
The existing
guest_modesection only covers the pre-Bot-API-10.0 @mention bypass. The native two-phase reply and media delivery behavior shipped in NousResearch#51886/NousResearch#52639 has no user-facing documentation, so operators have no way to know whatTELEGRAM_HOME_CHANNELdoes or why a "tap to receive" button shows up instead of an inline file.Requires
This PR documents behavior that doesn't exist on
mainyet — please merge those first, or review this as a preview of the docs that will land alongside them.How to test
cd website && npm run build(oryarn build) to confirm the docs page builds without broken links/MDX errors.Platforms tested
Docs-only change, no runtime platform testing applicable.
Mirror-of: NousResearch#56297
NousResearch#56297