A Discord Change for Custom-Bot Studios — and the One-Click Fix

Discord is changing which apps can read the text of messages. For most BetaHub users nothing changes — but if your bot runs under a custom name, there’s one quick, read-only action to take before September 9, 2026.

Am I affected?

Open your server’s member list and find your BetaHub bot:

• Named BetaHub 2, BetaHub 3, or your own studio’s name? → Yes — please add the reader bot below.
• Named just BetaHub, with a verification ✓? → No — you’re all set, nothing to do.

What’s changing

Reading message text is a privileged Discord capability — the Message Content intent — that only approved apps may use. The official BetaHub bot is approved; custom-named bots are not, so on its own your bot can no longer read messages.

That affects only the features that read what people write:

• Sentiment analysis
• Automatic bug & support detection
• Forum auto-creation (post → bug or suggestion)
• Reaction reporting (👍 / 🐛)

Everything else — slash commands, buttons, forms, DMs, and every notification your bot posts — keeps working with your bot alone.

The fix: one click, read-only

Add the official, verified BetaHub bot to the same server. It quietly reads messages and passes them to your bot, which stays the familiar face your community talks to.

• Read-only — it asks for just View Channels and Read Message History, nothing else.
• No new setup — it does not create a second project or start onboarding. Your bot and settings are untouched.
• Private channels — add it to any private channels where you use the features above.

Add the BetaHub reader bot →

Please do this before September 9, 2026.

What if I don’t?

Nothing breaks. Your bot keeps running and everything else works — you’ll simply lose the message-reading features above until you add the reader. You can do it any time.

Need help?

Not sure whether a server needs this, or run into a snag? Jump into our Discord and we’ll sort it out with you.

— The BetaHub Team