claude-code - 💡(How to fix) Fix Bring back token-by-token streaming (line-by-line streaming since v2.1.78 feels worse) [1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#53280Fetched 2026-04-26 05:19:44
View on GitHub
Comments
1
Participants
1
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×3commented ×1

Since v2.1.78 introduced line-by-line streaming, the visual experience of receiving text from Claude feels noticeably less smooth than the previous token-by-token streaming.

Root Cause

  • Reading along while Claude generates is harder when output appears in bursts.
  • Token-streaming made it easier to start parsing the response as it arrives.
  • The previous behavior was a quality-of-experience signature of Claude Code that matched the API's actual streaming granularity.
RAW_BUFFERClick to expand / collapse

Description

Since v2.1.78 introduced line-by-line streaming, the visual experience of receiving text from Claude feels noticeably less smooth than the previous token-by-token streaming.

Before (≤ v2.1.77)

Text streamed token-by-token, similar to claude.ai in the browser. Words appeared fluidly as they were generated, giving a "live writing" feel. Smooth and pleasant to follow.

After (v2.1.78+)

Text streams line-by-line. Whole lines appear at once, then a pause, then the next whole line at once. Within a line there is no progressive build-up — it pops into existence. This feels chunky/staccato and is harder to follow.

Why this matters

  • Reading along while Claude generates is harder when output appears in bursts.
  • Token-streaming made it easier to start parsing the response as it arrives.
  • The previous behavior was a quality-of-experience signature of Claude Code that matched the API's actual streaming granularity.

Request

Please add an opt-in setting / env var to revert to token-streaming, e.g.:

  • streamingMode: "token" in settings.json, or
  • CLAUDE_CODE_STREAMING_MODE=token

Defaults can stay as-is (line-streaming) — just give power users the choice.

Environment

  • Claude Code v2.1.119
  • macOS (Apple Silicon), Ghostty terminal
  • Default TUI renderer

Related

This is not the same as #37569 (which requests disabling streaming entirely). This issue requests reverting the granularity of streaming, not turning it off.

extent analysis

TL;DR

Add an opt-in setting to revert to token-streaming, allowing users to choose between line-by-line and token-by-token streaming.

Guidance

  • Investigate adding a streamingMode setting in settings.json to allow users to opt-in to token-streaming.
  • Consider introducing an environment variable CLAUDE_CODE_STREAMING_MODE to provide an alternative way to configure the streaming mode.
  • Review the current line-by-line streaming implementation to understand the changes made in v2.1.78 and how to revert to token-streaming.
  • Evaluate the impact of token-streaming on performance and user experience to ensure it does not introduce any regressions.

Example

No code snippet is provided as the issue does not contain sufficient technical details to create a accurate example.

Notes

The solution may require significant changes to the underlying streaming implementation, and careful consideration should be given to ensuring a smooth user experience.

Recommendation

Apply a workaround by adding an opt-in setting to revert to token-streaming, as this will allow power users to choose their preferred streaming mode while maintaining the default line-by-line streaming for other users.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Bring back token-by-token streaming (line-by-line streaming since v2.1.78 feels worse) [1 comments, 1 participants]