Agent view: high-rate terminal flicker in Windows Terminal (cmd.exe profile) while Claude is actively streaming

Status Fixed / completed
Reported on v2.1.144
Maintainer reply ✓ Yes — claude[bot]
Activity 3 comments · opened May 19, 2026 · closed May 21, 2026
💡 Likely answer: A maintainer (claude[bot], contributor) responded on this thread — see the highlighted reply below.

Environment

  • OS: Windows 11 Home Single Language (10.0.26200)
  • Terminal: Windows Terminal, Command Prompt (cmd.exe) profile
  • Claude CLI: 2.1.144

Description

In the claude agents view, after drilling into a conversation, the terminal flickers/redraws at a very high rate for the entire duration that Claude is active (processing/streaming a turn). The flicker stops and the screen settles as soon as Claude goes idle. It recurs on every subsequent prompt.

Steps to reproduce

  1. Launch Claude CLI on Windows 11 in Windows Terminal (Command Prompt profile)
  2. Open claude agents view and drill into a conversation
  3. Submit any prompt
  4. Terminal flickers continuously while the turn is active; settles once Claude is idle

Expected behavior

Stable rendering during streaming.

Actual behavior

Rapid full-screen flicker for the whole active turn.

Notes

  • Flicker duration correlates exactly with Claude's active/streaming state — this strongly suggests excessive full-screen redraws during the streaming render loop (spinner animation / output diffing) rather than a one-off resize glitch.
  • The 2.1.144 release notes mention reducing VS Code rendering glitches "by reducing spinner animation color count" and other Windows Agent View fixes — this looks like the same class of issue, currently unaddressed for Windows Terminal with the cmd.exe profile.

View original on GitHub ↗

3 Comments

github-actions[bot] · 3 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/60435
  2. https://github.com/anthropics/claude-code/issues/769
  3. https://github.com/anthropics/claude-code/issues/1913

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

claude[bot] contributor · 3 months ago

This issue was fixed as of version 2.1.146.

github-actions[bot] · 1 month ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.