telegram-bridge: append reply directive to inbound messages - #3
Open
bermudas wants to merge 1 commit into
Open
Conversation
Adds a TG_REPLY_DIRECTIVE suffix to every prompt forwarded from Telegram to a worker pane (single-target, broadcast, and attachment paths). The directive reminds the worker that: - the user cannot see the tmux pane - replying requires calling the notify MCP tool, not pane output - returned message_id should be quoted in taskbox/board references Without the directive, workers commonly reply in-pane and the user sees silence on Telegram.
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
Adds a
TG_REPLY_DIRECTIVEsuffix appended to every prompt forwarded from Telegram to a worker pane — single-target text, broadcast, and attachment paths. The directive reminds the worker that:mcp__notify__notify(message="..."), not pane output,message_idshould be quoted in taskbox/board references for traceability.Without it, workers commonly reply in-pane and the user sees silence on Telegram.
Ported from
MarketingFactory/octobots.Trade-offs
AGENT.md/CLAUDE.mdinstead of per-message. Per-message is harder to ignore but costs context every turn.message_idTelegram returns, which currently isn't surfaced by the localnotifytool — that's the MF-1 change (separate PR if we choose to port it). The directive still helps without it; the message_id sentence just becomes aspirational.Test plan
@role hellovia Telegram; confirm the worker prompt ends with the@all status(broadcast); confirm every worker prompt carries the directive.notifyto reply rather than printing to pane (manual observation).