feat(discord): add channel history tool#10736
Closed
zhouminmin0411-hub wants to merge 1 commit into
Closed
Conversation
Contributor
|
Thanks for the contribution @zhouminmin0411-hub! This is an automated hermes-sweeper review. The channel-history read capability you're adding here was implemented on
The separate |
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.
Summary
Why
Hermes can already send messages in Discord, but it cannot inspect the recent channel context on demand. This blocks instructions like look at the message Trouble sent above unless the user manually forwards the content.
This change adds a bounded read-history capability so Discord sessions can reference recent channel context directly.
Testing