FeverDream

FeverDream is a Discord bot that copies messages between servers, letting you mirror a channel live, bulk-repost an entire channel's history, or broadcast one…

  • Automation
  • Tools & Utilities
FeverDream is a Discord bot that copies messages between servers, letting you mirror a channel live, bulk-repost an entire channel's history, or broadcast one message to many channels at once. It preserves the original author's name and avatar via a dedicated "FeverDream Relay" webhook, and tracks repost progress with live /repost-status and /repost-stop commands. Channel links are saved locally and survive restarts, though in-progress repost jobs stay in memory and do not resume afterward. With no web interface and no ports to open, it runs headless and suits server admins and moderators relocating or syncing channels between communities.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

44/100 Fair

Maintained
77last commit 6 days ago
Popular
00 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
0
Open issues
0
Last commit
2026-11-15
License
MIT
Activity
rising

Checked 5 days ago - source: GitHub (catduckgnaf/discord-repost-history-bot)

Resources & Compatibility

Requirements not published yet.

Checked 5 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Enter your Discord OAuth2 client ID Before starting, replace YOUR_OAUTH2_CLIENT_ID with your Discord application's OAuth2 client ID, the unique ID Discord assigned to your app. If it's missing or wrong, Discord cannot identify your app or complete authorization. source
  • Allow Discord's permission popup On first launch, allow the Discord permission popup so the app can request basic user info (identify). If you deny or don't finish it, the bot cannot get the access token it needs from Discord. source
  • Install the app's npm packages In the project or server folder, run npm install; npm is the package downloader for Node.js apps. If you skip it, the bot may stop with missing-package errors before it can connect. source
  • Create the Discord application & bot token In the Discord Developer Portal, create a new application named FeverDream, open the Bot section, and click Reset Token to copy the new bot token. This token authenticates the bot with the Discord API and is the first value you enter when configuring it. source

Fetched 5 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Will reposted messages keep the original author's name and avatar?

Yes. The bot finds or creates a webhook named FeverDream Relay in the target channel and sends the message through it, so it appears to use the original author's name and avatar.

Do attachments stay usable after the original message is deleted?

Yes. Attachments are downloaded and re-uploaded with the library's Attachment.to_file() method, so they keep working even after the original message is gone.

Where are live channel forwarding links stored?

Persistent source-channel to target-channel links for live forwarding are stored in data/links.json, so links survive a bot restart.

Which slash commands manage channel links, bulk history reposts, and broadcasts?

/link-add, /link-remove, and /link-list manage channel links. /repost-history starts a bulk history repost, with /repost-status and /repost-stop for monitoring and stopping it. /broadcast sends one message to many channels at once.

Answers sourced from github.com

Community

Collected yesterday - public community threads