Skip to content

Enable Discord message intents and improve message logging#181

Open
Paraguanads wants to merge 4 commits intosipeed:mainfrom
Paraguanads:fix/discord-messaging
Open

Enable Discord message intents and improve message logging#181
Paraguanads wants to merge 4 commits intosipeed:mainfrom
Paraguanads:fix/discord-messaging

Conversation

@Paraguanads
Copy link

Enables the necessary Gateway Intents to receive message content and adds INFO logs to facilitate mention diagnostics. Fixes the issue where the bot connects but doesn't respond.

Key changes:

discord.go: Set Identify.Intents (GuildMessages, DirectMessages, MessageContent) and upload relevant logs to INFO.

Quick test:

Rebuild and install, start picoclaw gateway, mention the bot, and check for Raw message events / Received messages in the logs.

@PixelTux
Copy link
Collaborator

PixelTux commented Mar 4, 2026

@Paraguanads could you check if this still applies? If so, could you please resolve the conflict?

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

xuwei-xy pushed a commit to xuwei-xy/picoclaw that referenced this pull request Mar 14, 2026
…in toolloop, Discord MESSAGE_CONTENT intent, minimax config example
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

domain: channel type: bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants