First Run

This page walks through a first cleanup preview from discovery to execution.

This page assumes you already:

• installed the CLI
• authenticated with dmd login or DISCORD_TOKEN

1. Discover IDs first

dmd list guilds
dmd list channels

This shows the IDs you can pass to --include-ids. IDs can refer to guilds, categories, guild text channels, DMs, or Group DMs.

2. Start with dry-run

dmd clean --include-ids <id> --dry-run

--dry-run makes dmd fetch and evaluate messages without deleting messages or reactions. Use it to check the selected targets and retention rules before running the same command for real.

--include-ids accepts one or more IDs. Omit it to use the default scope: all eligible channels the tool can see.

By default, the run also removes your reactions and preserves nothing because:

• --keep-last defaults to 0
• --keep-within defaults to 0
• reactions are deleted unless you opt out with --keep-reactions

Dry-run reports per-channel planning details such as:

• messages and reactions that would be deleted
• scan time
• est. execute time
• est. total time

Check that the output matches your intent:

• the correct channel name
• a believable number of messages or reactions in scope
• a per-channel summary that matches your expectation
• no surprise channels in the output

3. Adjust the command

Common adjustments:

• Add --keep-within 2w if you want to protect recent history.
• Add --keep-last 20 if you always want to keep the last N messages in a channel.
• Add --fetch-within 2w1d later if repeated runs should only inspect a recent slice.
• Add --max-messages 100 if you only want to inspect a small recent slice first.

4. Execute when the plan looks right

Drop --dry-run once you are satisfied with the output:

dmd clean --include-ids <id>

If you want repeated cleanup over time, continue with Rolling Retention.