Streaming
Streaming is an AI UX pattern that reveals generated text token-by-token as the model produces it, instead of waiting for a finished response. It reduces perceived latency, proves the system is working, and lets users skim or stop early. Nearly every modern chat and coding assistant uses it.
When to use
Essential for all AI chat interfaces, text generation tools, and conversational AI applications where response time perception directly impacts user satisfaction.
When not to use
- Tiny deterministic outputs (a single number or yes/no) where streaming adds noise.
- Layouts that must paint as a complete unit (some charts or print-ready pages) until structure is known.
- Accessibility contexts where rapid token updates overwhelm screen readers without a “complete” announcement.
Anti-patterns
- No stop or cancel control while tokens stream.
- Layout thrash that jumps the page with every token.
- Streaming fake progress while the model has not started.
- Blocking copy/share until the full answer finishes when partial text is already useful.
How products use it
| Product | Implementation |
|---|---|
| ChatGPT | Token stream in the thread with stop generation during the run. |
| Claude | Streaming replies with interrupt and retry on the same turn. |
| Cursor | Streams code and chat; apply/diff flows wait for stable hunks. |
| Perplexity | Streams the answer while research steps and citations settle. |
Use this pattern in your project
Copy this prompt to generate a production-ready implementation in Cursor, Claude Code, Lovable, or any AI coding agent.
Generate a production-ready implementation of the "Streaming" AI interface design pattern.
Pattern Definition:Frequently asked questions
What is streaming in AI chat UX?
Streaming shows the model’s output as it is generated, usually token by token, so users see progress immediately instead of staring at a blank wait state until the full answer arrives.
Does streaming make the model faster?
Streaming mainly improves perceived performance. Time to first token feels faster even when total generation time is unchanged. Real speed still depends on model and infrastructure.
Should users be able to stop a stream?
Yes. A visible Stop control is table stakes. Users often know mid-answer that the direction is wrong and should not wait for a full wrong completion.
How should streaming work with screen readers?
Avoid announcing every token. Prefer polite live regions for start/complete, or a “response ready” cue, so assistive tech is not flooded during generation.