// 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 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 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.
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.
| name | events |
| description | 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 events to wake yourself up from background scripts or external triggers.
always include --chat-id <id> using the chat_id from your current session.
bun bob event --chat-id <id> "task_done" '{"result": "..."}' - signal success
bun bob event --chat-id <id> "task_failed" '{"error": "..."}' - signal failure
bun bob event --chat-id <id> "custom_event" '{"data": "..."}' - any custom event
when writing scripts, hardcode the chat_id so it knows where to send the event.
const CHAT_ID = 123456; // from current session
try {
const result = await doSomething();
await $`bun bob event --chat-id ${CHAT_ID} "task_done" '{"result": "${result}"}'`;
} catch (err) {
await $`bun bob event --chat-id ${CHAT_ID} "task_failed" '{"error": "${err.message}"}'`;
}
bun bob events list - see unprocessed events