BlackFlare

Telegram & Slack

Every notification BlackFlare produces — waiting, task finished, usage alerts, both providers — can also be forwarded to Telegram or Slack. That is what makes “walk away from your desk” actually work.

The per-event toggles on the Notifications tab decide what gets sent. The Delivery tab decides where.

Set up Telegram

  1. Message @BotFather on Telegram and create a bot. He hands you a token.
  2. Settings… → Delivery → Telegram, flip the toggle on. The config fields appear once the channel is enabled.
  3. Paste the bot token.
  4. Give it a chat: either type a chat ID directly, or send your new bot /start and click Detect chat.
  5. Hit Send test message.

Set up Slack

  1. Create an incoming webhook in your Slack workspace.
  2. Settings… → Delivery → Slack, flip the toggle on, paste the webhook URL.
  3. Hit Send test message.

Each channel section — Desktop, Telegram, Slack — shows a Configured / Not configured status pill, and surfaces its last delivery error inline as a red caption.

Only bother me when I’m away

Under Delivery options (which appears once a remote channel is on), smart away is on by default: BlackFlare forwards to Telegram and Slack only while you are actually away — screen locked, or no keyboard and mouse input for as long as you decide. Turn it off to forward everything regardless; “Send test message” always sends.

A Consider me away after field appears with the toggle: anywhere from 1 to 30 minutes, 2 by default. Both your idle time and the threshold are read at the moment a message would go out, so a change applies to the very next send. A locked screen counts as away immediately, whatever the field says.

Desktop banners are never gated by this. If you’re at the keyboard you get the banner; the phone stays quiet.

What to expect

  • Your secrets live in the Keychain. The bot token and webhook URL are stored as BlackFlare’s own Keychain items — never in UserDefaults, never in logs. Removing a channel deletes them. Because the items belong to BlackFlare, storing them triggers no consent prompt. The Settings fields show a fixed-length mask with an eye button to reveal.
  • Delivery is best-effort: one attempt, 10-second timeout, no retry and no queue. Failures are logged and shown in Settings. Desktop banners are unaffected by a remote failure.
  • Codex waiting alerts cover questions, not approvals. When Codex pauses to ask you a question, the waiting alert is forwarded like Claude’s; a session paused on an approval prompt sends nothing, because approvals never reach the rollout file (see Notifications) — the same limitation the desktop banners have.
← Back to BlackFlare