Integration overview
How it connects to OpenUI
The maintained harness delivers turns over Eve's native session protocol, resumes its event stream from a stored cursor, and translates Eve text, tool, and failure events into AG-UI for AgentInterface. The example uses an unauthenticated local Eve channel; a deployed version must configure channel authentication and appropriate tool permissions.
The integration path
- 1
Describe the interface
Generate a component prompt from the same OpenUI library that will render the response.
- 2
Stream structured output
Let Vercel Eve own its part of the stack while OpenUI Lang travels as incremental text or mapped agent events.
- 3
Render and interact
Parse the stream with the matching OpenUI runtime, render real components, and return validated actions to the application.
What stays consistent
One schema for prompting and rendering
Progressive rendering while output streams
Typed components instead of arbitrary markup
Host application retains its runtime behavior