# Render agent responses with OpenUI components

> Define the components an agent may render and review its actions before connecting real data.

Source: https://fullbytedeveloper.com/blog/openui-agent-component-rendering
Originally posted: 2026-10-19
Published here: 2026-11-06

OpenUI lets an agent stream interfaces made from components you register. Its repository documents typed component contracts and separate packages for rendering, chat state and backend integration. [1]

## Start with the rendering packages

For a React application, the README gives this installation: [1]

```bash
npm install @openuidev/react-lang @openuidev/react-ui
```

Follow the repository's getting-started example to define the component library and connect the renderer. Begin with a small set, such as a text block and a read-only result card.

## Treat actions as application input

A generated form or button still needs application code to validate its request and check authorization. I would test malformed values and an unauthorized action before connecting production data.

Inspect loading, empty and error states as well as successful output. Keyboard access and narrow-screen layout still belong to the application's review.

The current repository lists React, Vue, Svelte and Angular packages. [1] Check the package and examples for your framework; the versions mentioned in the older social post are not a current compatibility matrix.

## Sources

1. [OpenUI official repository](https://github.com/thesysdev/openui)

## Original posts

- [Instagram post](https://www.instagram.com/fullbytedeveloper/p/Der8y1_n4Cr/)