Skip to slide
096 / 221

CH 08 · Streaming and Real-Time UX · 01/11

Read as one page

Streaming and Real-Time UX

Streaming shapes an agent's transport, orchestrator, and data model, not just its interface. Covers SSE versus WebSockets and backpressure.

11 slides · 5 min read

Contour map for Streaming and Real-Time UX

In this chapter

  1. 01Why streaming is architectural
  2. 02The transport: SSE vs WebSockets
  3. 03The event-timeline pattern
  4. 04Streaming text while hiding machine protocol
  5. 05Ordering: flush before you act
  6. 06Surfacing reasoning
  7. 07Persisting the stream for replay
  8. 08Handling failures mid-stream
  9. 09Backpressure and connection management
  10. 10The payoff

Agents are slow by the standards of web requests; a single turn can take many seconds, involving several model calls and tool executions. If the user stares at a spinner the whole time, the agent feels broken even when it's working perfectly. Streaming is the answer, and it's not a cosmetic add-on: it's an architectural choice that shapes your orchestrator, your transport, and your data model. This chapter explains how to design a streaming agent.

Finished this idea?

Your learning progress stays in this browser.