.NET: MapAGUI supports per-request agent selection #2343
+73
−0
Conversation
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
github-actions
bot
changed the title
Copilot finished reviewing on behalf of
halllo
November 20, 2025 10:07
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR adds support for per-request agent selection to the MapAGUI endpoint routing functionality. Previously, agents were statically bound to endpoints; now, agents can be dynamically selected based on route parameters or other HttpContext data using a selector function.
Key changes:
- Added a new
MapAGUIoverload that accepts aFunc<HttpContext, ValueTask<AIAgent>>selector - Refactored the existing
MapAGUImethod to delegate to the new overload - Added sample code demonstrating dynamic agent selection using route parameters
Reviewed Changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 7 comments.
| File | Description |
|---|---|
| dotnet/src/Microsoft.Agents.AI.Hosting.AGUI.AspNetCore/AGUIEndpointRouteBuilderExtensions.cs | Added new MapAGUI overload with agent selector function and refactored existing overload to use it |
| dotnet/tests/Microsoft.Agents.AI.Hosting.AGUI.AspNetCore.UnitTests/AGUIEndpointRouteBuilderExtensionsTests.cs | Added basic test to verify endpoint mapping with agent selector function |
| dotnet/samples/AGUIClientServer/AGUIServer/Program.cs | Added example demonstrating per-request agent selection based on route parameter |
| dotnet/samples/AGUIClientServer/AGUIDojoServer/Program.cs | Added example demonstrating per-request agent selection with multiple agent types based on route parameter |
dotnet/src/Microsoft.Agents.AI.Hosting.AGUI.AspNetCore/AGUIEndpointRouteBuilderExtensions.cs
Show resolved
Hide resolved
halllo
force-pushed
the
AGUIOnDemandAgentSelection
branch
from
b2e6f0b to
3c8403e
Compare
halllo
force-pushed
the
AGUIOnDemandAgentSelection
branch
from
3c8403e to
7ec1c13
Compare
Author
|
@microsoft-github-policy-service agree |
halllo
changed the title
|
Nice, need this as well! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Motivation and Context
The current AGUI agent mapping binds one agent to an endpoint route. There is currently no way to bind an agent dynamically to an endpoint route with route parameters.
With this change we can select an
AIAgentper-request based on route parameters or anything fromHttpContext.This also addresses #2179.
Description
Additionally to providing an
AIAgentinstance directly during route building, we can now also provide aFunc<HttpContext, AIAgent>to determine theAIAgentper-request on-demand based on route parameters or anything fromHttpContext.Contribution Checklist