Integration overview
How it connects to OpenUI
The maintained local harness talks to Grok Build through its official Agent Client Protocol stdio mode, injects the generated OpenUI rules, and maps reasoning, text, tools, and interactions into AG-UI events for AgentInterface. As shipped, it is an unauthenticated single-user harness and needs authentication, sandboxing, and a stricter permission policy before networked deployment.
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 Grok Build 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