Repository navigation
.NET: fix(dotnet): register AG-UI interrupt content in server JSON options - #9007
Naveen Chatlapalli (1aifanatic) wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
The focused registration change resolves the reported serialization failure and is adequately covered by regression tests.
Review effort: Balanced
Findings: None
What changed in this PR
Registers AG-UI interrupt content types with ASP.NET Core JSON options, enabling human-in-the-loop messages to round-trip correctly.
Changes:
- Registers interrupt request and response content types.
- Adds regression tests covering both interrupt variants.
| File | Description |
|---|---|
dotnet/src/Microsoft.Agents.AI.Hosting.AGUI.AspNetCore/ConfigureAGUIJsonOptions.cs |
Registers interrupt content types with server JSON options. |
dotnet/tests/Microsoft.Agents.AI.Hosting.AGUI.AspNetCore.UnitTests/ConfigureAGUIJsonOptionsTests.cs |
Tests request and response interrupt round-tripping. |
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
0fcb272 to
ceaf9f0
Compare
|
Rebased onto current |
Motivation & Context
The JSON options installed by
AddAGUIServercannot serialize interrupt request/response content inside aChatMessage. This prevents callers using the configured options from round-tripping human-in-the-loop messages.Description & Review Guide
AGUIJsonUtilities.RegisterInterruptContentTypeskeeps this path consistent with the other AG-UI serializers. Both new tests failed before the change and pass afterward; all 14 tests in the affected project pass. The full .NET solution builds without warnings or errors. The full unit run had 9,167 passes, 69 skips, and three host-process failures; rerunning the affected LocalCodeAct and Shell projects separately passed all 120 and 118 tests respectively.Related Issue
Addresses the interrupt-content serialization portion of #8962. The separate null-field serialization report is already covered by open PR #7920; this change does not duplicate it or claim to close the entire issue.
Contribution Checklist