Summaries

A summary is a short digest of a project: what moved, what is stuck, what was decided and what comes next. It is written by an AI from the project’s Discord channels and its tickets in Linear (the tracker your team plans work in). It only uses channels you can see, and only you receive it.

Summaries are off unless whoever runs the bot has switched them on. If /summary does not appear in your server, they are off.

What a summary looks like

A scheduled summary arrives as a direct message: a headline, then up to four sections. Empty sections are left out.

Doge Bot sends you a DM

launch-daily - 10/01/2026 to 10/02/2026
Onboarding fixes shipped and the beta build is ready for testers

Progress

The onboarding flow fixes were merged and sent to testers (discord, ENG-12)
The beta build passed its smoke test (discord)

Blockers & risks

Audio drops out on one headset model (discord)
ENG-31 Crash when joining a full lobby is in review for 9 days (ENG-31)

Decisions

The next playtest moves to Thursday (discord)

Next

Retest the lobby fix once review is done

Line 1 is the summary name and the dates it covers, in your own date format. Line 2 is the headline.
Sections come in a fixed order: Progress, Blockers & risks, Decisions, Next. Each holds up to 8 bullets, except Blockers & risks, which can be longer because the bot adds stale tickets.
Links point to the Discord message or Linear ticket an item came from. Only links the bot adds are clickable.
Stale tickets: a ticket that has sat in Linear’s In Review status for 7 days or more is listed under Blockers & risks as ENG-31 Title is in review for 9 days, with a link. This is skipped if the bot cannot reach Linear.
Quiet period: with nothing to report you get No activity in this period.

A summary never pings anyone, even when it names a person or role. A long summary arrives as several messages, in order.

Who gets one, and when

You get a scheduled summary when an admin has added you, or a role you hold, as a recipient of it. You cannot sign yourself up: ask an admin. To see which summaries you can use, type /summary now and look at the list. Admins can read Summary configs for their side.

Schedule	When it arrives
Daily	At the summary’s send time on Monday to Friday. Not on Saturday or Sunday.
Weekly	At the send time on one chosen weekday.
On demand only	Never on a schedule. You ask for it with `/summary now`.

An admin picks the send time (ask them what it is). It is read in your own timezone, so teammates in other places get theirs at different moments. You need a timezone saved with /hours set; without one you get nothing on a schedule. See Timezone and working hours.

A scheduled summary covers the time since your last scheduled one, so the Monday summary includes the weekend. Summaries you ask for with /summary now do not move that starting point. If you have no earlier scheduled summary, or your last one is too old, it covers the last 24 hours (daily) or the last 7 days (weekly). Too old means more than 4 days and 1 hour for a daily summary, or 7 days and 1 hour for a weekly one.

It can arrive a few minutes after the send time, because the bot checks on a timer (every 15 minutes by default).

Ask for one now

/summary now writes a summary right away and shows it only to you. You can use it if you are a recipient of that summary or you have the Manage Server permission (the Discord permission admins hold).

config text required

Which summary. Start typing and pick from the list. The list only shows summaries you may use.

period choice optional

How far back to look. The period always ends now.

Default: 24h for a daily summary, 7d for any other Allowed: 24h, 7d, 14d, 30d

You type

/summary now config: launch-daily period: 7d

Doge Bot replies

launch-daily - 09/25/2026 to 10/02/2026
A quiet week: one fix shipped, two blockers open

Progress

The onboarding flow fixes were merged (ENG-12)

Blockers & risks

Audio drops out on one headset model (discord)
ENG-31 Crash when joining a full lobby is in review for 9 days (ENG-31)

Only you can see this

The reply shows up in the server, not in your direct messages. It is cut into pieces of at most 2000 characters, and extra pieces follow as more private messages. Writing takes a little while, so the bot first shows that it is working. If nothing has come after three minutes, it gives up and you can ask again.

What it is built from

Messages from the channels an admin linked to the project’s Linear team (the project’s channels). Deleted messages and messages from bots are left out.
Linear tickets for the same team, or one project of it: new, started and finished in the period, and anything in review. If the bot has no Linear connection, the summary uses messages alone.
An admin’s note: an optional line telling the AI what to stress, for example launch blockers.

The AI is told to use only what it found, to name where each item came from and to say “No activity” rather than guess. Treat it as a pointer to the real messages and tickets, and follow the links when it matters.

Only channels you can see

Your summary draws on a project channel only if you can open it and read its message history in Discord right now. The bot checks this each time it builds a summary.

If you lose access to a channel, it drops out of your next summary.
Having Manage Server does not show you more. The same rule applies to you.
If you can see none of the project’s channels, you get no scheduled summary, and /summary now tells you so.
If the bot cannot tell what you can see, it uses nothing.

Two people on the same summary can therefore get different content.

Replies you may see

You see	What it means
`There is no summary called "<name>". Pick one from the list that appears as you type.`	The name is wrong, or the summary is switched off. Pick from the list.
`You are not a recipient of this summary. Ask an admin to add you with /summary-admin recipients add.`	An admin has to add you or a role you hold.
`Summaries are not available: AI is not configured.`	The bot’s AI service is not set up. Tell whoever runs the bot.
`This command only works in the server.`	Run it in the server, not in a direct message.
`Please wait <N> seconds before asking for another summary. /summary now and /interests now share this limit.`	One request per person every 60 seconds, shared with `/interests now`. `N` is how many seconds are left.
`Busy right now, try again shortly.`	Three summaries are already being written. Try again in a moment.
`Daily summary limit reached, try again later.`	The bot writes only so many summaries a day, and this day’s allowance is used up. Try later.
`No channel mapped to this team is visible to you. Ask an admin to check /summary-admin list.`	You cannot see any channel this summary uses.
`I could not write that summary right now. Nothing was sent; try again in a minute.`	The AI failed. No summary text was kept, but the failed try still counts toward the bot’s daily limit. You can ask again at once.
`Something went wrong.`	An unexpected error. Try once more. Tell an admin if it repeats.

The 60 seconds start when you ask. If the request fails, the wait is cancelled and you can ask again at once.

Why you might not get a scheduled summary

Nobody is told when a scheduled summary is skipped, so check this list.

Reason	What to do
You are not a recipient, or your role is not.	Ask an admin.
No timezone saved.	Run `/hours set` with a `zone`.
It is a daily summary and it is Saturday or Sunday where you are.	Nothing. Monday’s covers the gap.
You are not in the server.	Nothing is sent to people who have left.
Your direct messages from the bot are closed.	Open them in your Discord privacy settings. The bot does not retry.
You cannot see any of the project’s channels.	Ask an admin which channels the summary uses.
The bot was off for more than an hour after the send time.	The missed summary is not sent later. Use `/summary now`.
The summary is switched off, or summaries are off for the whole bot.	Ask an admin.
Whoever runs the bot has limited its direct messages to a list of people and you are not on it.	Ask whoever runs the bot. `/summary now` still works for you.
The AI failed for that run, or twice gave an answer the bot could not use.	That send is not tried again. Use `/summary now`.
The bot hit its daily limit on summaries before it got to you.	Wait. The bot keeps trying for up to an hour after the send time. If the summary has not arrived by then, it will not come, so use `/summary now` later.
The summary is set to on demand only.	Use `/summary now`.
The bot’s AI service is not set up.	Tell whoever runs the bot.

Interests gives you a personal digest of the people, topics and channels you follow.
Timezone and working hours sets the timezone that decides when your summary arrives.
What the bot stores lists what the bot keeps about you and your messages.