Using workflow.AsAgent in combination with app.MapAGUI("/", agent);

[jakesduagile]

Using DI i have setup a few thing but mostly my workflow is setup during a request to our chat controller.

We have the capability to create an Agent from a Workflow
ie
var workflowAgent = workflow.AsAgent(id: "workflow-agent", name: "Workflow Agent");

My questions are

1. Whether it should be possible to map AG-UI to this Agent using app.MapAGUI("/", agent);

2. The issue I have is it seems that the AGUI registration happens at startup with builder ext. methods and my workflow gets created during runtime.

I'm not sure if I'm following the correct approach here and if I should create these workflows during setup as there is a couple of things that require runtime configs.

Any guidance in the right direction here will help.

Thank you

[Dazfl]

@jakesduagile - I have very similar questions.

I have set up a chat application, using AG-UI between my client and server, and I have set up a workflow to be the agent in .MapAGUI("/", workflowAgent).

My workflow is very simple - an Executor/Edge set up with a switch. I have an Intent Executor (which runs an Intent Agent), and if the intent is known, a Specialist Executor (which runs an agent) is called, otherwise an Error Executor is called.

However, I am getting this error - Workflow does not support ChatProtocol: At least List<ChatMessage> and TurnToken must be supported as input. I'm just not sure how set up my Executor(s) to handle this.

My questions are similar:

• Is it possible to run a workflow as an agent and use it for AG-UI
• If it isn't possible, what would be the recommended approach for this scenario?