[BUG] Terminal output has incorrect syntax highlighting - certain words appear highlighted unexpectedly

Resolved 💬 3 comments Opened Jan 21, 2026 by cjsimon2 Closed Jan 24, 2026

Preflight Checklist

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

What's Wrong?

aIn the terminal output, certain words are incorrectly highlighted/colored when they shouldn't be.

Affected words include:

  • verbose: (appears highlighted)
  • - ctx.console (appears highlighted)
  • - - dry_run (appears highlighted)
  • - - - show_progress (appears highlighted)
  • - - - - auto (appears highlighted)
  • - - - - - undefined (appears highlighted)

These words appear in regular prose text output from Claude, not in code blocks, yet they're being styled as if they were code/syntax elements. This makes the output harder to read and appears to be unintentional syntax highlighting being applied.

What Should Happen?

aRegular prose text in the terminal output should not have syntax highlighting applied. Words like verbose:, ctx.console, dry_run, show_progress, auto, and undefined should appear in the same color as the surrounding text when they are part of explanatory prose, not code blocks.

Error Messages/Logs

Steps to Reproduce

a1. Run Claude Code in the terminal

  1. Ask Claude a question that results in explanatory text mentioning variable names or programming concepts
  2. 3. Observe that words like verbose:, ctx.console, dry_run, show_progress, auto, and undefined appear with different coloring/highlighting than the surrounding text

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.12 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

<img width="1574" height="397" alt="Image" src="https://github.com/user-attachments/assets/9406761c-2622-4b5f-a8da-feb76b513f40" />

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗