Troubleshooting

Agent Can’t Read Discord Channels?

A fast fix for one of the most common setup traps: wrong guild ID, wrong channel ID, or channel permissions that silently block access.

If your agent says it can't read a channel (or keeps claiming a channel doesn't exist), this is usually an ID or permission issue — not an AI issue.

Most common failure: using a channel ID where a guild/server ID is expected, or copying IDs from the wrong server.

Quick 3-minute checklist

Confirm your guild ID is the server ID, not a channel/thread ID.
Confirm your channel IDs are from channels where the bot has access.
Verify permissions at both role level and channel override level.
Run one known-good test in a clean channel.

Step 1) Copy the correct IDs (exactly)

In Discord, enable Developer Mode, then right-click and copy IDs carefully:

Guild ID: right-click the server icon/title → Copy Server ID
Channel ID: right-click the channel name → Copy Channel ID
Thread ID: not the same as channel ID — avoid this unless your setup explicitly requires threads

Good example GUILD_ID=1471924346120568852 DISCORD_CHANNELS=1478816095941955779,1486377469715153121 Bad example GUILD_ID=1478816095941955779 # this is actually a channel ID

Step 2) Verify bot permissions in that exact channel

View Channel
Read Message History
Send Messages (if you want replies there)
Use Application Commands (for slash commands)

Even if role permissions look correct, a channel-level deny override can still block the bot.

Step 3) Check advanced Discord edge cases

Forum channels: make sure the bot can view the forum and create/view posts. A parent forum can be visible while post-level access still fails.
Private threads: thread IDs require explicit thread access. If your config expects channels, use the parent channel ID instead.
Category sync drift: if a channel is no longer synced to its category, old deny overrides can silently block the bot.
Role hierarchy: ensure your bot role is not effectively restricted by server role structure or integration restrictions.

Step 4) Run a known-good validation test

Create or choose one simple text channel
Grant explicit permissions to the bot role there
Use only that channel ID in your config
Restart/reload the agent session
@mention your agent with a short prompt

If this works: your model and core setup are fine. The problem is in ID mapping or channel-specific permissions in your original channels.

High-friction mistakes we keep seeing

Mixing up IDs after re-inviting the bot to multiple servers
Using private thread IDs when only parent channels are configured
Using forum post links/IDs instead of the parent forum channel ID
Bot appears online but cannot read due to hidden channel override
Channel permissions unsynced from category after manual edits
Copy/paste added spaces or punctuation around comma-separated IDs

Don’t rotate everything at once: change one variable at a time (guild ID, then one channel ID, then permissions) so you can isolate the exact failure.

Support packet (if still broken)

Post this in #help:

Discord channel access issue: - Guild ID used: [paste] - Channel IDs used: [paste] - Bot role perms checked: yes/no - Channel overrides checked: yes/no - Clean-channel test result: pass/fail - Error text from agent (exact): [paste]