set up

From nothing to a briefing every morning.

The path

1. 01spawn an agent

   @daimonrunbot

   Message the bot and send /spawn. It asks what the agent should do in plain language — the answer becomes its standing brief, so “keep track of what my teams are discussing and flag what needs me” is a better answer than a job title.

2. 02add it to the group

   your group

   Add @daimonrunbot the way you would add a person. That is the whole step — no admin rights to grant, nothing to configure in the group. It binds itself, switches memory on, and sends you a DM with a configure button.

3. 03ask, then stop asking

   @daimonrunbot, in private

   /digest all gives you one briefing across every group it watches, each point filed under the group it came from. When that reads the way you want, /digest daily on sends the same thing once a day without being asked.

Or run it under your own bot

A team that wants the agent answering under its own name can put it behind a bot they make themselves. Same features, three extra minutes, and two Telegram chores the main bot does not need — we already turned @daimonrunbot’s privacy off, so it reads group messages without being promoted; a fresh bot of your own has to be told.

1. 01make a bot

   @BotFather

   Send /newbot, pick a name, copy the token it gives you.

2. 02link it

   @daimonrunbot

   Send /link and paste the token. Your agent now answers as your bot, under your own name.

3. 03let it see the room

   your group

   Add your bot, then either make it an admin or send /setprivacy to @BotFather and turn privacy off. Telegram gives a bot ordinary group messages only under one of those two — this is Telegram’s rule, not ours. Then /groups to switch the group and its memory on.

What arrives

One message, once a day, at 07:00 UTC — each group under its own heading, and the things that want a decision from you called out as such. It is one model call across every group, not one per group.

your daily group digest:

In daimon: launch:
• API latency doubled after a recent deploy; the root cause was
  identified as the new index and a rollback was initiated.
• A new deployment plan is being prepared. No open decisions or
  direct actions required from you.

In daimon: partners:
• Acme requested a demo for Thursday and inquired about pricing tiers.
• The sales deck and a brief overview go out today. No decisions
  pending, but you may want to review materials going to Acme.

You can put a question on the end of any of them: /digest all what did they decide about the deploy?

If the summaries look thin

• your own bot cannot see the room. Only applies to the bring-your-own-bot route: Telegram hides ordinary group messages from a bot that is neither an admin nor privacy-off. Promote it, or send /setprivacy to @BotFather. @daimonrunbot is already privacy-off, so it never needs this.
• memory went on after the conversation. It only ever sees messages sent from that moment on — it does not read history it was not present for.
• two groups share a name. The picker shows a short handle after each of them so you can tell which row is which.