Enable Discord message intents and improve message logging#181
Open
Paraguanads wants to merge 4 commits intosipeed:mainfrom
Open
Enable Discord message intents and improve message logging#181Paraguanads wants to merge 4 commits intosipeed:mainfrom
Paraguanads wants to merge 4 commits intosipeed:mainfrom
Conversation
13 tasks
Collaborator
|
@Paraguanads could you check if this still applies? If so, could you please resolve the conflict? |
|
|
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.