com um clique
telegram
// telegram-specific inline directives you embed in your response text to react, reply-to, or control streaming. NOT a CLI tool - these are magic strings that get parsed out of your telegram response.
// telegram-specific inline directives you embed in your response text to react, reply-to, or control streaming. NOT a CLI tool - these are magic strings that get parsed out of your telegram response.
use when user wants to enable do not disturb, go afk, not be messaged for a while, or is going into a meeting/appointment. triggers include "afk", "dnd", "do not disturb", "don't message me", "going into a meeting", "be back in", "brb".
use when writing background scripts that need to notify you on completion or failure, or when you need to wake yourself up immediately from an external trigger. triggers include "background task", "script finished", "notify on complete", "wake me when done", "event hook", "callback", "on error", "on success", and similar.
use when you need to remember something, recall past decisions, look up what the user told you before, store preferences, save important facts, or search your memory for context. triggers include "learn", "remember", "forget", "recall", "what did i say", "did i mention", "store", "save", "memory", "notes", "log", and similar.
use when you need to set a reminder, schedule a task for later, create recurring jobs, check back on something in the future, or wake yourself up at a specific time. triggers include "remind me", "in an hour", "tomorrow", "every day", "later", "follow up", "check back", "schedule", "timer", "alarm", "recurring", "cron", and similar.
| name | telegram |
| description | telegram-specific inline directives you embed in your response text to react, reply-to, or control streaming. NOT a CLI tool - these are magic strings that get parsed out of your telegram response. |
how it works: embed these directives anywhere in your response text. they get parsed out and executed - the user won't see the directive syntax, just the result.
these are NOT CLI commands. you literally type [[react: 👍]] in your response and it becomes a reaction.
react to a message without sending a reply text:
[[react: 👍]]
that's it - just the directive, nothing else. user sees a 👍 reaction on their message.
common reactions: 👍 👎 ❤️ 🔥 😂 😢 🤔 👀
use when:
reply threading - your message appears as a reply to theirs:
[[reply_to_current]] yeah i see what you mean
or reply to a specific message by id:
[[reply_to: 12345]] responding to that earlier point...
control how your response appears as you generate it:
[[stream: edit]] starting to work on this...
modes:
edit - update the same message as you type (default)send - send chunks as separate messagesoff - wait until complete, then send oncehandled something that doesn't need user notification:
NO_REPLY
combine with react for silent acknowledgment:
[[react: 👍]] NO_REPLY
telegram supports: bold, italic, code, code blocks, links, strikethrough