[Feat] Remember routing corrections for ambiguous tasks#748
Draft
roomote-roomote[bot] wants to merge 2 commits into
Draft
[Feat] Remember routing corrections for ambiguous tasks#748roomote-roomote[bot] wants to merge 2 commits into
roomote-roomote[bot] wants to merge 2 commits into
Conversation
Contributor
Author
|
No new code issues found. See task
Reviewed 955bc1c |
Contributor
Author
|
Fixed in 955bc1c: Slack |
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
env:<id>selection value before comparing it to the routed environment, so an unchanged reroute does not train memory.Why this change was made
Users often correct ambiguous routing decisions toward the environment they prefer. Those corrections should help resolve future ambiguity without allowing past preferences to override current task intent.
Impact
Ambiguous requests can now route to a user's recent, repeatedly corrected environment. Confident or explicitly scoped requests retain their normal routing outcome, unchanged Slack reroutes no longer inflate preference weight, and classifier fallbacks never train the preference memory.