summarizes a single group. with several groups on, it asks which one — or takes the all-groups row at the top.
docs
What did I miss? Ask once.
Add your agent to a Telegram group, turn memory on, and it keeps a short rolling log of what was said. Then ask it — in your own private chat — what happened. One question covers every group it watches, and it can send that summary to you unprompted, once a day.
The three commands
one summary across every group your agent has memory on for, each point attributed to the group it came from. one model call, not one per group.
the same combined summary, dm'd to you once a day at 07:00 UTC. off by default. /digest daily off stops it.
You can add a question to any of them: /digest all what did they decide about the deploy?
Turning it on
- add the bot to the group.it binds to your agent and posts a notice in the group, then memory starts. if the notice can't be posted, memory stays off and you can retry from /groups. you get a dm with a configure button.
- no admin rights needed. @daimonrunbot already has privacy off. only a bot you made yourself must be an admin or have privacy off in @BotFather; otherwise it sees just the messages that mention it, and the summaries will be thin.
- tune it in /groups (optional): how far back it keeps (6 hours to 7 days), group replies, or memory off. the notice in the group says memory is on — see “who gets told” below.
- ask. /digest all in your private chat with the bot.
What it remembers, and for how long
- 01only what it saw — a telegram bot cannot read anything sent before it joined, or while memory was off. that is a bot API limit, not a setting — there is no way around it.
- 02a window, not an archive — text only, and only what falls inside your window (24 hours unless you change it). anything older is deleted, and a group never keeps more than its newest 1000 messages. turning memory off deletes that group's log immediately.
- 03one window per group — a digest reads everything said inside the window you set in /groups: 6 hours, 24 hours (default), 3 days or 7 days. shortening the window deletes what falls outside it right away. if a window holds more than one digest can read, it summarizes the most recent messages and tells you so.
- 04never across owners — an agent only ever reads groups bound to itself. one owner's group content can never reach another owner's agent, and your private chat with the agent never enters a group answer.
Who gets told
Group members did not sign up for Daimon, so switching memory on is disclosed to them, in the group, before anything is kept. The bot posts this — and if it cannot post, memory does not turn on:
heads up — kerem's agent dani.daimon just turned on group memory here. i'll keep a rolling log of the last 24 hours so i can summarize recent discussion for kerem. i only see messages sent while i'm in the group, and turning memory off deletes the log.
Summaries go to you privately by default. If you want the agent to answer inside the group as well, turn on group replies in /groups.
What it costs
Keeping the log is free — no model call, no charge. A digest is one model call the agent pays for out of its own balance, whether you asked for it or it fired on the daily schedule. A combined digest over four groups is still one call.
Every group carries its own daily spend cap (0.50 USDC by default, adjustable in /groups) and its own rate limit. A group that has hit either is left out of the read entirely — its members' messages are not sent to a model on spend it cannot pay for — and the digest tells you when that happened:
covered 2 of 4 groups — 1 at their daily cap or rate limit, 1 had nothing new in their window.
You only see that line when the digest was short of the full set. Full coverage says nothing, because there is nothing to disclose.
The daily one
/digest daily on arms one summary a day, delivered to your private chat at 07:00 UTC. It is off until you arm it — along with the auto digest below, one of the two digests that fire on a timer.
It stays quiet when there is nothing to say: no messages inside the window, or every group at its cap, means no dm rather than an empty one. It runs once per day even if the service restarts, and it obeys the same per-group caps as a digest you ask for yourself.
The auto one
/digest auto on sends a summary of each group once per memory window, before its oldest messages are deleted: a 6-hour group about every 6 hours, a 7-day group about weekly. Each one covers only what was said since the previous digest, so nothing is repeated, and a quiet group is skipped without a charge or a dm. It is off until you arm it, it bills and obeys the caps like any other digest, and /digest auto off stops it. With the daily digest on as well, a message is covered by whichever fires first, never by both.