Conversation core
Message thread
Use when users will copy, rate or regenerate an answer, and need earlier versions to stay within reach.
User and assistant turns with hover actions and response branches.
Part of Conversation core. The first thing you build: a place to ask and a place to read the answer. Every AI product ships these surfaces, so users compare yours with the best they have used. The work here is in the details: what the composer does mid-answer, how a reply arrives, what you can do with it afterwards.
Do
- Keep the actions out of the way until the pointer is on the reply, then show them in one row.
- Keep every regenerated version and show a pager, so a retry never destroys the answer before it.
- Confirm a copy in place with a tick that clears itself.
Don't
- Don't give the agent a bubble. The user's turn is the bubble, the agent's reply is plain text beside its glyph.
- Don't ask why on a thumbs down here. Use Feedback capture when you need a reason.
- Don't rely on hover alone on touch screens. Show the action row permanently there.
States
- Resting: The user's message in a bubble with its time, and the agent's reply as plain text beside the agent glyph.
- Hovered: An action row appears under the reply: copy, retry, thumbs up, thumbs down, the version pager and the time.
- Copied: The copy icon becomes a green tick for a little over a second.
- Rated: The chosen thumb stays highlighted. Choosing it again clears the vote.
- Another version: Retry or the pager arrows cross-fade to a different reply and the counter updates, for example 2 / 3.
Usage
import { MessageThreadPattern } from "./halaska-kit";
<MessageThreadPattern />
Built from
Agent Glyph, Message, Stack, Typography
Related patterns
Streaming answer, Feedback capture
Halaska UI · Components · Patterns · Screens · Install