claude-code - 💡(How to fix) Fix [BUG] TUI emits strikethrough on arbitrary text - reproduces on 2.1.150 in both diff view and normal output

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

When using claude cli it displays random ascii characters after using it a while.

What Should Happen?

Preflight Checklist

• I have searched existing issues and this hasn't been reported in this specific form
• This is a single bug report
• I am using the latest version of Claude Code

What's Wrong?

The Claude Code TUI is rendering arbitrary text with strikethrough formatting where none was intended. It appears the renderer is emitting ANSI SGR 9 (or equivalent) around tokens that should not be styled at all.

This is NOT limited to the diff renderer. It fires in normal assistant chat output as well.

Two distinct repro patterns observed in the same session:

1. Diff view, JavaScript keywords: In an added-line diff block (green/plus lines), the bare keywords if and return render with a full strikethrough across the word. No surrounding tildes, no markdown syntax, no ~ characters anywhere in the line. The strikethrough is applied directly to the keyword tokens.

2. Normal assistant output, underscored identifier in parentheses: In a regular response paragraph, a parenthesized identifier like (wp_wqly_qlx_qmu_...) renders with strikethrough applied to every single character including the underscores. Surrounding text in the same line ("Backend", "now short-circuits") renders normally.

This appears related to but distinct from the GFM tilde-as-strikethrough reports in #19251 and #9757, both of which are currently marked stale. Those issues describe literal ~text~ wrapping triggering strikethrough. This report covers text that does not contain tildes at all.

What Should Happen?

Text should render without strikethrough unless the source content explicitly uses ~~strikethrough~~ GFM syntax. JavaScript keywords in diff output and underscored identifiers in normal prose should render as plain text with normal syntax highlighting.

Steps to Reproduce

Exact trigger is not yet isolated, but the bug fires reliably during:

• Reviewing proposed file edits where the diff contains JS keywords like if / return / function
• Reading normal assistant responses that include parenthesized identifiers with underscores

The bug persists across:

• New sessions
• /clear
• Restarting Claude Code
• Restarting the VS Code integrated terminal

Claude Code Version

2.1.150

VS Code Extension Version

2.1.150 (IDE bridge server 2.1.145)

Model

Opus 4.7 with 1M context

Platform

Anthropic API (Claude Max account)

Operating System

Windows 11

Terminal/Shell

VS Code integrated terminal on Windows 11

Additional Information

Reproduces on the latest CLI, latest VS Code extension, and current IDE bridge, so the differential renderer rewrite from late January 2026 did not address this case.

Related stale issues:

• #19251 (GFM tilde-as-strikethrough, reopened Jan 2026, stale)
• #9757 (original tilde-as-strikethrough, closed and locked Oct/Nov 2025)

Both describe the tilde-input case. This report adds a non-tilde input case that the existing reports do not cover. Screenshots attached showing both manifestations.

Error Messages/Logs

Steps to Reproduce

Use Claude CLI

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

Claude Code CLI: 2.1.150 VS Code extension: 2.1.150 (server 2.1.145) Model: Opus 4.7 (1M context) OS: Windows 11 Terminal: VS Code integrated terminal Login: Claude Max

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information