[Fix] Coding tasks reply directly when Fast owns the conversation - #1804
Draft
roomote-roomote[bot] wants to merge 1 commit into
Draft
[Fix] Coding tasks reply directly when Fast owns the conversation#1804roomote-roomote[bot] wants to merge 1 commit into
roomote-roomote[bot] wants to merge 1 commit into
Conversation
Contributor
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.
What changed
communicationContextInheritedWhy this change was made
Fast owns user communication for orchestrator-delegated coding tasks, but direct reply suppression previously depended only on the newer
communicationContextInheritedflag. Persisted or partially migrated child payloads can still be recognized throughreportConsumerorfastAgentParent; treating those existing signals as authoritative prevents duplicate or out-of-band coding-task replies.Impact
Orchestrator-owned coding tasks report only to their parent session across Slack, Discord, Teams, and Telegram, including older payload shapes. Direct chat tasks continue using their existing provider reply paths. This PR does not change provider intake: draft PR #1792 continues to own Teams Fast-first task entry, Telegram intentionally retains normal inbound task routing, and Slack/Discord bot or webhook auto-starts retain their existing identityless fallback policy.
Validation
pnpm lintpnpm check-typesgit diff --check