tldr;
- Use
<C1Component>when you want to render UI from the C1 API inside any app surface (dashboards, tools, internal apps). - Use
<C1Component>if you already have a text based chat interface and want to migrate to Generative UI. Check out the migration guide on how to migrate easily. - Use
<C1Chat>when you want a full conversational UI (history, roles, avatars, message list) plus everything<C1Component>can render.
Detailed Comparison
C1Component
<C1Component> is the fundamental frontend component that renders C1 DSL into
a functional micro-frontend. It support streaming & actions and can be
used in a variety of applications (like dashboards, canvas, embedded widgets)
beyond chat.
C1Chat
<C1Chat> is built on top of <C1Component> and besides besing able to
render the C1 responses it also includes abstractions to thread management,
persistence and a out-of-the-box chat experience.
Comparison Matrix
| Capability | <C1Component> | <C1Chat> |
|---|---|---|
| Render C1 DSL → UI | ✅ | ✅ |
| Streaming UI | ✅ | ✅ |
| Forms & actions | ✅ | ✅ |
| Message history (UI & state) | ➖ (DIY) | ✅ Built-in |
| Roles (system/user/assistant) | ➖ (via API) | ✅ First-class |
| Chat UI (bubbles, avatars, input) | ➖ | ✅ |
| Persistence helpers | ➖ | ✅ Guides available |
| Best for | Apps & dashboards | Chatbots & agents |