discord-history-exportlisted

# Discord History Export > **Caveat (ToS)**: Discord's Terms of Service forbid automating user accounts ("self-botting"), even for actions the user could perform by hand. The exporter sends one HTTP request per `before=` page, paced by DCE's built-in rate-limit handler — risk to a normal account doing a one-off export is low but non-zero. The skill must surface this to the user before any token is captured, and must offer the GDPR data-export route as an alternative. > **Caveat (token)**: The user's token grants full account access (DMs, settings, payments). It appears in the conversation transcript during this skill. After export, instruct the user to change their Discord password — this invalidates the token immediately. ## When To Use - User has joined a Discord server and wants a local copy of every channel they can read - User wants ONE specific channel exported (skip the guild-wide walk; use the `export` subcommand instead of `exportguild`) - User wants a JSON dataset to grep / analyze / feed into another LLM - User wants an HTML archive that renders identically to Discord (avatars, attachments, replies, emoji) ## When NOT To Use - Target is a **Group DM** (multi-person private chat) — Discord blocks Bot accounts from joining and self-bot detection is denser here. Use the official GDPR data export instead: Settings → Privacy & Safety → Request my Data. - User is a **server administrator** and willing to invite a Bot — that path is ToS-compliant. Hand off to the use