Agent GUI standalone? #1349
Description
Contact Details
No response
What should we build?
We currently have a built in chat interface in the orchestrator-ui-library.
Considering we are splitting up the agent from the core package, do we also split it up from the orchestrator-ui-lib?
And if so, do we have requirements on what stack we should use. For example, we currently use copilotkit, but we do not use all features extensively, it might not be so hard to recreate this with our own chat component.
All we need I think is a hook that captures the various ag-ui events, and renders them to whatever we want.
Because there are some downsides to copilotkit too. It does not seem to be maintained well, tickets are open for months and core team does not respond to them, even though some of these tickets should be high prio.
Keeping it standalone but with ag-ui, means developers can still connect their own copilotkit frontend.
Some open issues I (and others) have had problems with:
Global css imports:
CopilotKit/CopilotKit#2851
OnError behind paywall:
CopilotKit/CopilotKit#2249