telegram-bridge: forward reply context to workers - #2
Open
bermudas wants to merge 1 commit into
Open
Conversation
When a user replies to a worker's Telegram message, include the quoted
text in the prompt sent to the worker pane so it can resolve
pronoun-style replies ("yes", "rerun", "do the other one") instead of
guessing from session memory.
Upstream uses the [role] badge in the quoted text only to resolve
routing and then discards the content. This change strips the badge
and prepends `(reply to: "...")` to the forwarded prompt for both text
messages and file attachments.
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
[User via Telegram] (reply to: "<quoted>"): <new text>.[role-name]badge prefix is stripped from the quoted text before forwarding so the worker doesn't see noise.Upstream behavior used the badge in the reply only to resolve routing (which role the user wanted to reach) and then discarded the quoted content. The worker therefore got
[User via Telegram]: rerun pleasewith no idea what "rerun" referred to. This change preserves the context.Ported from
ChildrenHomeWork/octobots.Test plan
(reply to: "...")context.@role <message>(no reply) still uses the unchanged[User via Telegram]:prefix.