fix(discord): use parent channel_id in SenderContext when in thread#583
Merged
thepagent merged 1 commit intoopenabdev:mainfrom Apr 26, 2026
Merged
Conversation
|
All PRs must reference a prior Discord discussion to ensure community alignment before implementation. Please edit the PR description to include a link like: This PR will be automatically closed in 3 days if the link is not added. |
github-actions
Bot
added
closing-soon
…penabdev#581) When a message is received inside a Discord thread, the agent now gets the parent channel ID as channel_id and the thread's channel ID as thread_id. Previously, channel_id contained the thread ID since Discord treats threads as separate channels. Closes openabdev#581
chaodu-agent
force-pushed
the
fix/581-sender-context-channel-id
branch
from
04ad67f to
be54d80
Compare
This was referenced Apr 26, 2026
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
3 participants
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
Fixes #581 — agent receives thread ID instead of channel ID in
SenderContext.Changes
When a message is inside a Discord thread, the
SenderContextnow provides:channel_id: the parent channel ID (where the thread was created)thread_id: the thread's channel IDPreviously both were conflated —
channel_idcontained the thread ID andthread_idwas alwaysnullfor Discord.How it works
The thread detection match arm already resolves
gc.parent_id. This PR captures it and uses it when constructingSenderContextfor in-thread messages.Testing
openab-zhoudududeployment on OrbStack — confirmed the bug viaacp_sendlogs showing thread ID inchannel_idfieldCloses #581