Skip to content

Comments

docs: strengthen Telegram notifications to MUST when bridge active#205

Open
v4lheru wants to merge 1 commit intomainfrom
docs/telegram-must-notify
Open

docs: strengthen Telegram notifications to MUST when bridge active#205
v4lheru wants to merge 1 commit intomainfrom
docs/telegram-must-notify

Conversation

@v4lheru
Copy link
Collaborator

@v4lheru v4lheru commented Feb 20, 2026

Summary

  • Changes soft "when to notify" guidance to explicit MUST requirements when the Telegram bridge is active
  • Adds concrete message examples for each notification trigger
  • Clarifies what NOT to notify for (routine internal steps)
  • Bridge remains fully optional — only enforced for users who opt in

Why

Agents were inconsistently sending Telegram notifications because the instructions used descriptive language ("when to notify") rather than imperative ("you MUST notify"). Users who set up the bridge expect to be kept informed.

Changes

  • Heading: "Optional" → "Optional — but MANDATORY when available"
  • Added: "notifications are NOT optional — they are REQUIRED"
  • "When to notify" → "You MUST send telegram_notify" with example formats
  • Same for telegram_ask and telegram_check_replies
  • Added "Do NOT notify" section to prevent spam

🤖 Generated with Claude Code

…ge active

Changes soft "when to notify" guidance to explicit MUST requirements.
When users opt in to Telegram, agents should reliably notify for
completions, blockers, PRs, and deployments — not treat it as optional.

Adds concrete examples for each notification trigger and clarifies
what NOT to notify for (routine internal steps).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant