DevUI - do I have to register the agents during DI?

[itayfisz]

Context

I am building a .NET Aspire application using the Microsoft Agent Framework.
Instead of registering static Agents in the DI container at startup, I create the agents on runtime. This is necessary because the agents depend on system prompt that's constructed dynamically, and using async methods (you can think as if the prompts are loaded from some remote location).

The Problem

The current DevUI setup (e.g., app.MapDevUI / MapAGUI) seems to expect agent instances to be ready and registered during the application startup pipeline.

Since my agents are created on-demand and asynchronously, I cannot easily map them during Program.cs startup without blocking the main thread.

The Question

Is there a supported interface (like an IAgentProvider or IAsyncAgentLoader) that can be used to "feed" agents to the DevUI lazily?

[codehunter13]

yes you need to construct them using DI. It's not needed to create the agents at runtime. Create them using DI. Then just use AIContextProvider to create the system prompt at runtime.
This way you prob also don't need async calls in DI

[itayfisz]

I understand why DevUI would want it during the DI - to set the endpoints and everything. I wonder design-wise it would really be preferred to register each agent in the DI.
If someone has any thoughts on that, I'd love to hear

[codehunter13]

Think the question is Why not? Do you still have reasons?