By Alex, who builds Cuelark. The components linked here are ours.
A chat screen looks finished long before it behaves properly. Put a few bubbles above a textarea and it photographs well. Then somebody presses Enter twice, cancels a response, or pastes a file they did not mean to attach.
That is where I would start a React AI chat interface. Not the gradient. The state transitions.
We built Cuelark components for this layer of the application: a message layout and a composer you can adapt in your own project. They are UI source, not an AI backend. They do not choose a model, protect a secret API key, or make your data handling private by themselves.
This walkthrough focuses on the boundary between those pieces. Getting that boundary right makes the rest of the interface much less surprising.
Use source you can change
The shadcn approach is useful here because a chat interface rarely stays generic.…