Try run MAF workflow as an agent on DFx

[thangchung]

Ref:

• https://techcommunity.microsoft.com/blog/appsonazureblog/bulletproof-agents-with-the-durable-task-extension-for-microsoft-agent-framework/4467122
• https://learn.microsoft.com/en-us/agent-framework/user-guide/agents/agent-types/durable-agent/create-durable-agent?pivots=programming-language-csharp
• Run workflow as an agent: https://learn.microsoft.com/en-us/agent-framework/user-guide/workflows/as-agents?pivots=programming-language-csharp

[thangchung]

Look at microsoft/agent-framework#1092 (reply in thread)

Graph-based workflows offer a more declarative authoring experience with higher-levels of abstraction. The visualization tools you get are a really nice benefit of the graph-based authoring approach if graph-based visualizations are important for you and your development team.

Function-based durable execution workflows (durable orchestrations) offer a more imperative authoring experience where you manage control flow and state changes more explicitly. This can be ideal if you and your team prefer to work at lower levels of abstraction and prefer to analyze code vs. visualizations.

And,

Both Pregel supersteps and Durable Task orchestrations are orchestration patterns, but they differ in their execution models. Pregel uses graph-based, message-passing execution with synchronized supersteps, while Durable Task uses imperative code (async/await ) for long-running, distributed workflows. They serve complementary purposes: Pregel for in-process graph workflows, Durable Task for distributed, serverless scenarios.

This is a fundamental architectural difference between the two orchestration systems:
Pregel workflows are optimized for fast, in-process graph execution with message passing, while Durable Task orchestrations are built for distributed, long-running workflows that can span multiple machines and survive process restarts.

[vmdt]

In Microsoft Agent Framework (MAF), app.MapA2A(...) only accepts an ITaskManager, not an AIAgent.

If a workflow is implemented as an AIAgent (for example, a composite workflow agent that orchestrates other agents), how can it be hosted and exposed as an A2A Agent Server?