fix(discord): do not comment on Jira or GitHub unless asked - #426
Merged
Conversation
Discord turns inject linked Jira keys as context. Agents treated that as a request to post completion summaries on the ticket. Reply only on the originating surface unless the user explicitly asked. Co-authored-by: Enrico Polanski <16064771+enricopolanski@users.noreply.github.com>
omegent-app
Bot
force-pushed
the
fix/discord-reply-surface-lock
branch
from
August 27, 2026 07:01
b99a94f to
da7a2c9
Compare
Author
|
The 2026-08-26 t3vm deploy auto-stash ( Stashed paths:
They match this PR’s docs 1:1. Rebased onto latest Opened from this Discord follow-up by patroza. |
patroza
enabled auto-merge (squash)
August 27, 2026 07: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.
Discord turns inject linked Jira keys as context. Agents treated that as a request to post completion summaries on the ticket (example: unsolicited Omegent comment on SA-438, now deleted).
Reply only on the originating surface unless the user explicitly asked. Opening a GitHub PR for landable work is still allowed; commenting on Jira/GitHub/Confluence is not.
Test plan
vp test runthreadContext + T3AgentRulesvp checkopened by enricopolanski in chat thread Discord · Discord