Beacone
Launching soon

Only the GitHub notifications that matter.

Beacone watches the repositories you choose and forwards to Telegram the notifications that matter.

Beaconebot
🔔 Review requestedacme-analytics/ingest-api#412 — “Retry failed webhook deliveries with backoff”
15:38
🔔 You were assignedacme-analytics/dashboard#1187 — “Session expires mid-export”
15:43
Message

Three steps, then never again

Setup once, use forever.

  1. Sign in

  2. Install the App where you want

    Your account or an organisation, all repos or a handful. Beacone sees exactly what you installed it on — nothing more.

  3. Tap once in Telegram

    One deep link opens the bot and links the chat. There is no ID to copy and nothing to type.

You decide what counts as important

GitHub already tells us why it notified you. Beacone turns that reason into a switch — tick the ones worth a buzz, leave the rest on github.com where they belong.

Three reasons are wired up today, and they are the three that mean somebody is waiting on you. Then mute the specific bots, people and repositories that still get through — bots are muted from the moment you sign up.

  • Bots muted by default
  • Mute any account
  • Mute any repository
  • Review requestedYou were asked, by name, to review a pull request.
  • MentionSomeone wrote your @handle.
  • AssignedAn issue or pull request was assigned to you.
  • Team mentionSomeone mentioned a team you belong to. Not built yet.
  • Watched repositoryAnything at all in a repository you watch on GitHub. Not built yet.
  • CI activityA workflow run you triggered finished. Not built yet.
Working today

A deleted comment doesn’t leave a lie in your chat

Somebody @-mentions you, thinks better of it, and deletes the comment. Most tools have already sent you the ping and will happily send a second one about the deletion.

Beacone reaches back into the message it already sent and strikes it through, with a note saying who removed it. No second ping, and nobody who missed the original hears about it at all. That is the one amendment built so far — the rest of the list is where this is going, not where it is.

  • comment.deletedstruck through
  • comment.editednot built yet
  • pull_request.mergednot built yet
  • review.dismissednot built yet

Three read permissions. That is the entire ask.

Beacone never clones your code, and it stores notification metadata only — who, where, which thread. Not the diff, not the comment body.

  • Metadata: Read

    Names of the repositories the App is installed on.

  • Issues: Read

    So an assignment or a mention on an issue can reach you.

  • Pull requests: Read

    So a review request reaches you before the day is over.

  • No contents access · no clones
  • No OAuth scopes on sign-in
  • Delete your account and everything goes with it

Questions

Does it work with private repositories?
Yes. Access comes from installing the GitHub App on the account, not from your sign-in — private repos included, if you tick them.
How fast is it?
Webhooks, not polling. GitHub pushes the event the moment it happens and the message is on its way in the same request.
Can I use it on an organisation?
Install it there like any GitHub App. If you are not an owner, GitHub files the request with the people who are.
What will it cost?
Nothing while it is in beta. If a paid tier arrives, you will hear before it does.
Slack or Discord instead?
Telegram only, today. It is the one that reaches a phone without a work account. Nothing else is built, and there is no date for one.
Can I turn it off for a while?
Untick every reason, mute the repository, or disconnect the account entirely — one button, and every trace of your data goes with it.

Be there when it opens.

One email when the doors open, and nothing else. No card, no drip campaign.