Route appmod prompt to local agent provider - #12253
Merged
Merged
Conversation
|
Azure Pipelines: Successfully started running 1 pipeline(s). There may be pipelines that require an authorized user to comment /azp run to run. |
fangjian0423
approved these changes
Jul 29, 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
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 does this implement/fix? Explain your changes.
This pull request updates the Java Upgrade notification service to ensure that Java upgrade prompts are always routed to the local Copilot agent, improving reliability and compatibility with custom agents. The main changes involve adding a new helper method and integrating it into the query builder logic using reflection for backward compatibility.
Copilot Agent Routing Improvements:
withLocalAgentProviderthat pins queries to the local Copilot agent provider using reflection, ensuring the Java Upgrade prompt uses the correct agent. This method gracefully handles older Copilot plugin versions by silently skipping if the required API is unavailable.withLocalAgentProvidermethod into the Copilot query builder flow, so all Java upgrade prompts are explicitly routed to the local agent.Minor cleanup:
AzureTelemeterfromJavaVersionNotificationService.java.Does this close any currently open issues?
Any relevant logs, screenshots, error output, etc.?
Any other comments?
…
Has this been tested?