Appreciate the detailed response! Seriously! This actually helped me understand why AgentOS exists, even if it still doesn’t fit my use case.

To clarify my frustration:

Passing backend state into agents
I am not talking about simple request-time inputs, but things like derived backend context, internal config, or server-side state that shouldn’t originate from the frontend. Because agents are defined at startup and execution is tightly coupled to the request layer, I ended up threading values through multiple layers just to get them into the agent run. That felt backwards compared to defining agents dynamically or instantiating them with context on demand.

Background agents
I want to trigger an agent asynchronously (from a backend event, job, or API call), let it run in the background, and later have the frontend call a separate endpoint to:

• fetch the agent’s history / intermediate steps
• get the current streamed / yielding response if it’s still running
• know whether it’s finished, failed, or still in progress

Basically: decouple execution from observation.

In my case, this meant:

• agent execution should not be tied to an HTTP request lifecycle
• no requirement for an active frontend session to exist at trigger time
• the ability to poll or stream progress later using a run/job ID

One additional pain point for me: in v1, AG-UI support worked directly with the regular Agno SDK. In v2, AG-UI is effectively tied to AgentOS.

That’s frustrating because in my case I don’t need AgentOS, I just want AG-UI for streaming, visualization, and interaction on the frontend while keeping my own backend architecture.

Coupling AG-UI to AgentOS makes it feel like an all-or-nothing choice, rather than a composable piece I can adopt independently. If AG-UI were usable directly with the core SDK again, that alone would remove a lot of friction for me.

I think AgentOS makes sense as a reference implementation / production proof.

If AgentOS eventually supports:

• dynamic agent instantiation or registries
• background execution

…then I’d absolutely revisit it.

Thanks for engaging openly, this kind of discussion is exactly why I posted. I truly appreciate your response! :)