Incorrect syntax highlighting/escaping of Windows backslash paths in terminal output

Open 💬 2 comments Opened Mar 1, 2026 by Barry2llen
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex CLI is running?

codex-cli 0.106.0

What subscription do you have?

GPT Plus

Which model were you using?

gpt-5.3-codex

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What terminal emulator and version are you using (if applicable)?

pwsh(PowerShell 7)

What issue are you seeing?

In a Windows Environment (PowerShell), the CLI's output highlighting incorrectly treats the backslash \ in file paths as an escape character. This leads to inconsistent syntax coloring where parts of the path are rendered in different colors or interpreted as escape sequences rather than literal strings.

<img width="2349" height="1221" alt="Image" src="https://github.com/user-attachments/assets/1049fb82-eb0f-453d-901d-4013053efa52" />

What steps can reproduce the bug?

  1. Run a command that includes a Windows-style path.
  1. Observe the terminal output generated by the CLI.

What is the expected behavior?

The entire path string should be recognized as a single literal path entity and colored consistently.

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 5 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #13151

Powered by Codex Action

Barry2llen · 5 months ago

I've fixed the bug in my local branch. @etraut-openai