Discord hides channels a bot can't view, from November 16, 2026 over HTTP

Announced12 Aug 2026

Effective16 Nov 2026

Time left3 days

What changed

On August 12, 2026 Discord announced that bots will follow the same rule as users for channels they lack VIEW_CHANNEL on. Over the Gateway such channels are still dispatched but obfuscated: the name becomes ___hidden___, sensitive fields are nulled or reduced and the CHANNEL_OBFUSCATED flag (1 << 17) is set. Over HTTP, GET /guilds/{guild.id}/channels will omit those channels entirely starting November 16, 2026, with no early opt-in. Gateway testing is available now through the 1 << 15 Identify capability or a Developer Portal toggle. Interaction payloads are not obfuscated.

What it means

From November 16, 2026 the list of a server's channels returned to a bot leaves out every channel the bot lacks View Channel on, so a scheduler's channel picker may show fewer channels.

Who is affected

Scheduling tools and bots that list a Discord server's channels so users can choose where to post, and bots that audit or mirror channel lists.

What to do by 16 Nov 2026

Treat the channel list as only the channels your bot can view. If a channel is missing, ask the server admin to give the bot View Channel there. Test the Gateway behavior with the CHANNEL_OBFUSCATION capability now.

What this means for you

When you connect a posting tool to a Discord server, it shows you the channels you can post to. From November 16, 2026, Discord will only show the tool channels its bot is allowed to see. If a channel goes missing from the list, the bot needs permission to view that channel. Nothing changes for channels the bot can already see.

The details

HTTP (from November 16, 2026): GET /guilds/{guild.id}/channels "will omit those channels from the response entirely." There is no early opt-in for HTTP.
Gateway: channels the bot can't view are still dispatched with name set to "___hidden___", other sensitive fields nulled or reduced, the CHANNEL_OBFUSCATED flag (1 << 17), and a single overwrite denying VIEW_CHANNEL for @everyone. Only id, type, position and parent_id are reliable.
Testing now: send 1 << 15 in the capabilities field of Identify, or enable "Private Channel Obfuscation" under Overview > Bot in the Developer Portal. Both are temporary.
Regaining access: when the bot gains VIEW_CHANNEL, a Channel Update event carries the full channel data.
Interactions: payloads are built separately and are not obfuscated.
Who is affected: "If your bot only acts in channels it has permission to view, this change does not affect you."

What to do next

Business owners: If your scheduler stops showing a Discord channel after November 16, 2026, give the bot's role View Channel in that channel.
Marketers and agencies: Before November 16, 2026, check that the posting bot can view every channel you schedule to in each client server.
Developers: Detect obfuscation with the CHANNEL_OBFUSCATED flag, not the name, test with the Identify capability now, and show users a hint when a channel they expect is missing.

Follow new entries with the RSS feed. Each platform also has its own feed, for example X or Meta.