Get back to caught up.

1. Add Summary Bot to Discord and choose a server where you have permission to install apps.
2. In any text channel you can read, type /catchup.
3. Summary Bot starts from your saved place, or offers a useful initial range if this is your first catch-up.
4. Use the result’s source links to open the underlying messages, or use Recast to reshape the same result.

No API key or configuration is required. Server admins can run /setup later to choose defaults and privacy settings.

The install link requests only the Discord permissions needed to read permitted conversations and deliver useful result cards:

Summary Bot separately checks the requesting member’s channel access. Granting the Bot access does not allow a member to summarize channels they cannot read. A server admin can block a channel for everyone with /privacy channel.

Check these in order:

1. Confirm Summary Bot can View Channel and Read Message History in the source channel.
2. Confirm it can Send Messages and Embed Links where the response should appear.
3. For threads, confirm it can Create Public Threads and Send Messages in Threads.
4. Confirm the person running the command can access every requested source channel.
5. Run /permissions to see the Bot’s diagnostic view.
6. Ask a server admin whether the channel was blocked or the server was restricted through /privacy.

Start with the coverage line on the result. It reports the number of messages and time span considered. A result may omit content because it fell outside the requested range, was in a channel the requester or public audience could not access, came from an opted-out member, or exceeded the plan’s message range.

Use the command’s range and depth options for a different pass. Pro and Scale can use server scope. If the result is correct but shaped poorly, choose Recast rather than fetching the channel again.

Run /usage to see the server plan, monthly allowance, top-up balance, and recent credit use. Every completed AI action also reports the credits charged and the remaining server balance.

One credit covers 35 characters of raw message content, rounded up per message, plus a fixed write price for the selected quality. If a request is estimated above 3,000 credits, Summary Bot pauses and asks for confirmation.

Top-ups purchased through Discord do not move to a server automatically. The purchaser must run /usage and choose “Apply purchased credits here.”

Discord processes Summary Bot Premium App purchases. Summary Bot never receives your full payment-card details.

• To cancel a subscription, follow Discord’s Premium App cancellation guide. Use the same device type used to start the subscription.
• For refund eligibility and requests, review Discord’s Refund Policy and contact Discord support.
• Removing Summary Bot from a server does not automatically cancel its Discord subscription.

• /privacy info explains what the Bot reads and stores.
• /privacy optout removes your messages from summaries in that server.
• /privacy welcome controls welcome summaries for your profile everywhere.
• /privacy forget deletes the identifiable profile data Summary Bot holds about you.
• /privacy channel lets admins block a channel for every user.
• /privacy restrict lets admins require Manage Server for summary commands.

Read the full Privacy Policy for message processing, stored data, service providers, and retention.

/ask answers from accessible conversation context and includes citations to supporting Discord messages. The mention agent can reason in a thread and prepare actions; any tool that writes waits for explicit confirmation.

If a source link does not open, confirm that the message still exists and that your Discord account can access its channel. Public recap sources are limited to channels visible to the full audience.

Join the support server and include:

• the command or feature you used;
• the approximate time and your timezone;
• what you expected and what happened instead;
• the stable failure code or trace ID shown by Summary Bot; and
• whether the issue is repeatable.

Do not share message transcripts or credentials unless support explicitly requests a narrowly scoped detail in a private channel.