---
id: "contrarian-streaming-is-state"
type: "contrarian-insight"
source_timestamps: ["00:13:56"]
tags: ["llm-streaming", "observability", "contrarian"]
related: ["concept-structured-streaming-events"]
challenges: "The conventional view that LLM streaming is purely a UI/UX feature for text generation."
sources: ["s46-anthropic-25b-leak"]
sourceVaultSlug: "s46-anthropic-25b-leak"
originDay: 46
---
# Streaming is for State, Not Just Text

## The Contrarian Position
Conventionally, LLM streaming is used merely to provide a typewriter effect in a UI. Nate argues that in agentic systems, **streaming must be used to emit structured, typed events** that communicate the model's internal state and tool usage in real time.

## What This Challenges
The conventional view that LLM streaming is purely a UI/UX feature for text generation.

## Supporting Concept
Fully developed in [[concept-structured-streaming-events]]. Example event types include `message_start`, `command_match`, and `tool_match`.

## Counter-Evidence (from Enrichment)
Redis and Vellum engineers argue that streaming optimizes time-to-first-token (TTFT) and UX, but adds backend complexity — state-sync overhead can exceed 20ms per event. Not every system needs structured streaming if its observability requirements are modest.

## Defensible Synthesis
Streaming serves **two purposes**:

1. **UX** — token-by-token rendering for users.
2. **Observability / control** — typed events that let the backend monitor and intervene on the model's chain of thought.

Production agentic systems should support both. The contrarian point is that **most teams stop at #1**, missing the architectural value of #2.