Description
Describe the feature you're requesting
I'd like Microsoft Agent Framework's AG-UI integration to support the native AG-UI interrupt/resume workflow for Human-in-the-Loop interactions.
Currently, the C# documentation demonstrates a custom approval tool pattern (for example, request_approval) instead of emitting the standard AG-UI interrupt events and resuming execution through the AG-UI protocol.
What problem does it solve?
When building an AG-UI client, developers expect Human-in-the-Loop approvals to work through the standard AG-UI interrupt lifecycle. Because MAF currently uses a custom tool-call pattern instead, clients must implement custom handling for approvals rather than relying on the AG-UI interrupt protocol.
This means:
- Additional frontend code is required to recognize synthetic approval tool calls.
- The frontend cannot rely on the standard AG-UI interrupt/resume lifecycle.
- Applications that already support AG-UI interrupts need Microsoft-specific handling.
- It makes interoperability with other AG-UI implementations more difficult.
- The current approval workflow makes it difficult for AG-UI clients to manage and display multiple pending Human-in-the-Loop requests using the standard interrupt model.
Expected behavior
When a Human-in-the-Loop approval is required, Agent Framework should emit the standard AG-UI interrupt events. After the user approves or rejects the request, the client should resume execution using the standard AG-UI resume mechanism without requiring a synthetic approval tool.
This would allow AG-UI clients to:
- Use a single interrupt/resume implementation across AG-UI-compatible backends.
- Manage Human-in-the-Loop interactions using the standard AG-UI protocol.
- Display and manage multiple pending interrupts in a consistent way, where supported by the backend.
- Reduce custom frontend logic required specifically for Microsoft Agent Framework.
Alternatives considered
The current documented approach works, but it requires implementing a custom approval workflow and additional frontend logic that deviates from the AG-UI interrupt model.
Supporting native AG-UI interrupts would improve interoperability, reduce custom code, and make it easier for developers building AG-UI clients to integrate with Microsoft Agent Framework.
Code Sample
Language/SDK
.NET
Description
Describe the feature you're requesting
I'd like Microsoft Agent Framework's AG-UI integration to support the native AG-UI interrupt/resume workflow for Human-in-the-Loop interactions.
Currently, the C# documentation demonstrates a custom approval tool pattern (for example,
request_approval) instead of emitting the standard AG-UI interrupt events and resuming execution through the AG-UI protocol.What problem does it solve?
When building an AG-UI client, developers expect Human-in-the-Loop approvals to work through the standard AG-UI interrupt lifecycle. Because MAF currently uses a custom tool-call pattern instead, clients must implement custom handling for approvals rather than relying on the AG-UI interrupt protocol.
This means:
Expected behavior
When a Human-in-the-Loop approval is required, Agent Framework should emit the standard AG-UI interrupt events. After the user approves or rejects the request, the client should resume execution using the standard AG-UI resume mechanism without requiring a synthetic approval tool.
This would allow AG-UI clients to:
Alternatives considered
The current documented approach works, but it requires implementing a custom approval workflow and additional frontend logic that deviates from the AG-UI interrupt model.
Supporting native AG-UI interrupts would improve interoperability, reduce custom code, and make it easier for developers building AG-UI clients to integrate with Microsoft Agent Framework.
Code Sample
Language/SDK
.NET