Skip to content
This repository was archived by the owner on Jul 23, 2026. It is now read-only.

telegram-bridge: append reply directive to inbound messages - #29

Open
bermudas wants to merge 1 commit into
arozumenko:mainfrom
bermudas:feat/telegram-reply-directive
Open

telegram-bridge: append reply directive to inbound messages#29
bermudas wants to merge 1 commit into
arozumenko:mainfrom
bermudas:feat/telegram-reply-directive

Conversation

@bermudas

Copy link
Copy Markdown
Contributor

Summary

Append 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 mcp__notify__notify(message="..."), not pane output,
  • the returned message_id should be quoted in taskbox/board references.

Without this, workers commonly reply in-pane and the user sees silence on Telegram.

Trade-off

Adds ~300 chars per inbound message — context bloat over long chat sessions. The directive could alternatively live in each agent's AGENT.md/CLAUDE.md, but per-message is harder to ignore.

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.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant