[BUG] Garish progress bar at top of screen appeared in 2.0.52 or .53

---

Found 1 possible duplicate issue:

1. https://github.com/anthropics/claude-code/issues/12345

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 Code's analysis of the diff between 2.0.51 and 2.0.53:

Found the bug!

  The issue is with the OSC 9;4 terminal progress indicator - a feature that shows a progress bar in the terminal's
  title bar or tab (supported by ConEmu, Ghostty, and some others).

  What Changed

  In v2.0.51 (cli.js:403280-403330):
  class O81 {
    isAvailable() {
      if (!process.stdout.isTTY) return !1;
      if (S0.terminal === "windows-terminal") return !1;
      let A = S0.terminal?.toLowerCase();
      return A === "conemu" || A === "ghostty";  // ← Only ConEmu/Ghostty
    }
    report(A) {
      if (!this.isAvailable()) return;  // ← Guard check
      // ... outputs OSC 9;4 sequence
    }
  }

  In v2.0.53 (cli.js:220760-220780):
  // New general rendering pipeline
  case "progress":
    B += o06(G.state);  // ← NO terminal compatibility check!
    break;

  function o06(A) {
    // Directly outputs OSC 9;4 to ALL terminals
    return `${lb1}9;4;${Q};${G}${f3A}`;  // \x1b]9;4;...
  }

  The Problem

  The terminal compatibility check was removed in v2.0.53. The OSC 9;4 sequence (which creates the progress bar
  effect) is now being sent to all terminals, not just ConEmu and Ghostty which support it.

  Your terminal doesn't understand this escape sequence, so instead of showing a progress bar in the title/tab area,
  it's rendering the escape codes as visual garbage - the "green scrolling gradient progress bar" you're seeing.

  Workaround

  Until this is fixed, you could try:
  1. Set TERM_PROGRAM or another env var that might trick the detection
  2. Downgrade to v2.0.51
  3. Use a terminal that supports OSC 9;4 (Ghostty, ConEmu)

  This appears to be a regression bug where the refactoring to a new rendering pipeline lost the terminal capability
  check.

Closing - #12620 resolved this.

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.