Repository navigation
Federated Agentic UI: a component catalog assembled at runtime from micro frontends #3160
lutzleonhardt
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone 👋
I built a demo that explores one question: what if the component catalog isn't fixed, but assembled at runtime?
In real apps, the building blocks an agent should be able to use often depend on context: the user's permissions, the device, the tenant's license, feature flags. So in this demo, every component comes as a capability with two halves:
Capabilities are delivered by Native Federation remotes, so separate teams can ship them independently. If a capability is loaded, the model can use it. If it isn't, the model doesn't know the component exists and tells the user what it can't show instead of improvising. Neither the shell nor the agent server is rebuilt or redeployed.
In the video: same prompt twice. Without the maps capability, the assistant says it has no map component. With it, you get an interactive map with a working distance slider.
hero-linkedin.mp4
**Some details: **
Stack: Angular,
@a2ui/angular, CopilotKit, AG-UI, Mastra, Native Federation. The base architecture follows Manfred Steyer's book "Agentic UI with Angular".What do you think? Like to hear your feedback :)
All reactions