Syntax highlight code in CLI

readability issue they should style that so they help us read its hard to read

Claude Code has syntax highlighting

<img width="796" height="373" alt="Image" src="https://github.com/user-attachments/assets/8af596ee-b2ef-43db-90b6-52b0706c9622" />

Cursor CLI also has some nice syntax highlighting.

<img width="892" height="490" alt="Image" src="https://github.com/user-attachments/assets/dc0238a0-2903-43d5-82aa-e4c1e7004ad3" />

That's right, Codex appearance looks raw, hopefully Codex have styling beautiful as Claude's code with elegant textbox, responses, and syntax highlighting

<img width="1920" height="1053" alt="Image" src="https://github.com/user-attachments/assets/7a034d54-6575-4a2d-9a57-a55f5a4441c5" />

<img width="1920" height="1048" alt="Image" src="https://github.com/user-attachments/assets/8f65f802-5dc5-4db3-b3ae-2eb98bd7252a" />

After switching to GPT-5.1, the model's responses have become extremely long, which has resulted in very poor readability. Looking at the plan makes my eyes hurt.

Oofa, just started using Codex CLI and yeah... this was a disappointment.

I am not a Rust programmer and I just engineered this with Gpt 5.2 codex high

https://github.com/SamSaffron/codex/commit/707f356f37f6c40ecd32db7bc8c72be745ce0f50

The result though is quite nice.

<img width="1560" height="1918" alt="Image" src="https://github.com/user-attachments/assets/1c6e2fa7-cdc6-4bd1-ba2e-555b75619d7b" />

I feel like it is quite significant in that it makes the experience much more polished for Codex users.

I am not a Rust programmer and I just engineered this with Gpt 5.2 codex high SamSaffron@707f356 The result though is quite nice. <img alt="Image" width="1560" height="1918" src="https://private-user-images.githubusercontent.com/5213/532685343-1c6e2fa7-cdc6-4bd1-ba2e-555b75619d7b.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Njc3Njg5OTgsIm5iZiI6MTc2Nzc2ODY5OCwicGF0aCI6Ii81MjEzLzUzMjY4NTM0My0xYzZlMmZhNy1jZGM2LTRiZDEtYmEyZS01NTViNzU2MTlkN2IucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI2MDEwNyUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNjAxMDdUMDY1MTM4WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MWQxYjQ5Y2JhNWI3MGYxOGIyMGQ4ZTI0Nzg0YmRkMzFjMWYyNjk5ZDhkYzkxZTU3OWQ4NDU0ZGRmYTQ1NDNkZSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.dejSv7yZTD1AcvK2rjPpMAmK3YSI-i5X1wT0A1ahkkM"> I feel like it is quite significant in that it makes the experience much more polished for Codex users.

I think the issue isn't just with the code rendering; the Markdown used for the planning phase isn't very readable either.

I think the issue isn't just with the code rendering; the Markdown used for the planning phase isn't very readable either.

exactly

> I think the issue isn't just with the code rendering; the Markdown used for the planning phase isn't very readable either. exactly

I've switched to OpenCode, and it works very well with GPT.

I can’t believe this issue still hasn’t been resolved after half a year.

@Sure-Will, we generally prioritize features based on community upvotes. If you'd like to see this feature, please add a thumbs-up reaction. That will move it higher in the priority list.

I implemented syntax highlighting in my fork, xCodex (xcodex), and shipped it in v0.3.5.

What it does:

• Syntax-highlights fenced code blocks in the transcript (themeable).
• Also supports diff highlighting in the transcript (separate toggle).

Languages supported (v0.3.5):
Bash (bash/sh/zsh), C, C++, CSS, Go, HTML, Java, JavaScript, JSON, Python, Ruby, Rust, TypeScript, YAML.

How to try:

• Install: npm i -g @eriz1818/xcodex
• Toggle in TUI: /settings transcript syntax-highlight toggle

(or config.toml: [tui] transcript_syntax_highlight = true)

• or via /settings menu

Docs:

• Settings: https://github.com/Eriz1818/xCodex/blob/main/docs/xcodex/settings.md
• Release notes: https://github.com/Eriz1818/xCodex/blob/main/docs/xcodex/releases/0.3.5.md
• Theming/token roles: https://github.com/Eriz1818/xCodex/blob/main/docs/xcodex/themes.md

<img width="2056" height="1153" alt="Image" src="https://github.com/user-attachments/assets/f8e4cac5-9c00-4281-be08-ed64c893f009" />

For this I'd like to see us use Arborium https://fasterthanli.me/articles/introducing-arborium

The main blocker on this might be release artifact size - it's about 30mb of deps, but due to the way we package for npm right now (I think) we produce a single npm artifact for all targets rather than one per target. I could be wrong about that (haven't looked at it in a while.

<img width="1855" height="1849" alt="Image" src="https://github.com/user-attachments/assets/57695087-6214-47c6-9ab7-f2f43918dd58" />

In fact, a very similar issue has been ranked number 4 for a long time. #

@Sure-Will, we generally prioritize features based on community upvotes. If you'd like to see this feature, please add a thumbs-up reaction. That will move it higher in the priority list.

@Wan9xy, yes this features will rise in the priority list as we close other features that had even more upvotes. This feature (syntax highlighting) is distinct from #1618.

This will be included in the next release!

This will be included in the next release!这将在下一个版本中包含！

Thanks for your hard work!