[Improve] Match Discord unmentioned thread replies to Slack gating#568
Merged
mrubens merged 2 commits intoJul 18, 2026
Merged
Conversation
Apply Slack/Teams-style eligibility and interjection rules so natural follow-ups in Discord task threads stop requiring drive-by side chat to be treated as agent turns.
Contributor
Author
…Teams Extract eligibility and interjection-window evaluation into a single pure helper so the three providers stay behavior-aligned without duplicating the decision loop.
mrubens
approved these changes
Jul 18, 2026
mrubens
marked this pull request as ready for review
July 18, 2026 22:05
mrubens
deleted the
improve/discord-slack-style-unmentioned-gating-331ulqlc2lfwj
branch
July 18, 2026 22:05
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
1 participant
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.
What changed
Discord task threads now use the same unmentioned follow-up rules as Slack:
@mention) only work for people already in the conversation: the task owner, the thread starter, or someone who tagged Roomote earlier in the thread@mentionedafter Roomote’s last reply, the next human message needs an@mentionagain@mentions, DMs, and/newstay on the normal entry pathThe eligibility + interjection decision loop is shared across Slack, Discord, and Teams in
apps/api/src/handlers/shared/unmentioned-thread-reply.ts. Provider modules only handle provider-specific preconditions, history mapping, and provider-specific side effects (Slack explicit-mention footer/redis flag). Public Discord docs were updated too.Why this change was made
Discord previously treated every linked user’s unmentioned message in a known task thread as an agent turn. That made multi-person side chat hijack the task. Sharing the decision core keeps Slack/Discord/Teams from drifting.
Impact
In active Discord task threads, drive-by and multi-person chatter no longer becomes agent work unless you
@mentionRoomote. Solo task follow-ups keep working without a mention when you’re an eligible participant. Slack and Teams continue current behavior through the shared helper.