claude-code - 💡(How to fix) Fix [Bug] Terminal output lag and duplication in Claude Code TUI rendering

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…

Fix Action

Fix / Workaround

Impact: The lag forces a workaround where the assistant ends up issuing extra no-op commands (e.g. echo markers) just to "flush" the pending output and confirm what landed — which adds noise and wastes turns. It also makes it genuinely difficult to verify results before acting on them.

Environment: - OS: Arch Linux (kernel 7.0.9-arch2-1) - Shell: bash - Long-running session with frequent multi-tool turns and large tool outputs - The problem worsens as the conversation/context grows; it was not clearly fixed by /compact, which suggests it's a terminal/harness rendering issue rather than a context-size issue.

Code Example

[]
RAW_BUFFERClick to expand / collapse

Bug Description Terminal rendering issues / output lag and duplication in Claude Code

I'm experiencing persistent rendering problems in the terminal UI during long sessions:

1. Output lag: Tool results (Bash command output, Read tool output) don't appear in sync with the
tool call that produced them. They arrive one turn late — I run a command, the assistant
continues, and the result from the previous call shows up underneath the current one. This makes
it very hard to follow what's actually happening.
2. Duplicated / out-of-order output: The same tool output sometimes renders multiple times, and
blocks appear out of the order they were executed in. A single Read or Bash result can show up two
or three times in the scrollback.
3. Garbled rendering: Output occasionally appears corrupted/interleaved, especially when multiple
tool calls run in the same turn or when results are large.

Impact: The lag forces a workaround where the assistant ends up issuing extra no-op commands (e.g.
echo markers) just to "flush" the pending output and confirm what landed — which adds noise and
wastes turns. It also makes it genuinely difficult to verify results before acting on them.

Environment:
- OS: Arch Linux (kernel 7.0.9-arch2-1)
- Shell: bash
- Long-running session with frequent multi-tool turns and large tool outputs
- The problem worsens as the conversation/context grows; it was not clearly fixed by /compact,
which suggests it's a terminal/harness rendering issue rather than a context-size issue.

What would help: Confirmation of whether this is a known issue with the TUI rendering pipeline,
and whether it's related to terminal emulator, output buffering, or the way concurrent/large tool
results are streamed and reconciled. (Terminal: Ghostty)

Environment Info

  • Platform: linux
  • Terminal: ghostty
  • Version: 2.1.159
  • Feedback ID: 4bd778d8-3581-4948-882a-fb1c413336ba

Errors

[]

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 [Bug] Terminal output lag and duplication in Claude Code TUI rendering