VS Code Expose Codex internal syntax highlighting theme (used in chat panel & Codex app)

Resolved 💬 1 comment Opened Mar 26, 2026 by DiamondNectar Closed May 10, 2026

What variant of Codex are you using?

App, IDE Extension

What feature would you like to see?

Problem

Codex already uses a consistent syntax highlighting theme for code rendering:

  • in the Codex App
  • in the VS Code extension (chat panel code blocks)

However, this theme is not available as a selectable/editor theme in VS Code.

Currently, there is no way to:

  • apply the same syntax highlighting to the editor
  • reuse the Codex theme outside of chat/code blocks
  • export or reference this theme

---

What I want

I want to use the exact same syntax highlighting theme that Codex uses internally:

  • for chat code blocks
  • in Codex App

…as my main editor theme in VS Code.

---

Expected behavior

One of the following:

  1. Expose the Codex theme as a VS Code theme (e.g. "Codex Theme")
  2. Add a setting in the extension:
  • "codex.useEditorTheme": true
  1. Allow exporting the internal theme (JSON / TextMate rules)
  2. Document the token color mappings used by Codex

---

Why this matters

The Codex theme already exists and is well-designed.

Using a different theme in the editor creates inconsistency:

  • chat panel → one syntax style
  • editor → another

This breaks visual continuity and developer experience.

---

Additional context

This is not a request for a new theme —
the theme already exists inside Codex.

The request is to make it reusable in the editor.

---

Workarounds tried

  • Manual editor.tokenColorCustomizations
  • Using existing themes (One Dark Pro, etc.)

These do not match the Codex theme exactly.

---

Suggestion

Expose the internal Codex theme as:

  • a built-in VS Code theme
  • or a JSON export

This would ensure consistency across:

  • Codex App
  • VS Code extension (chat)
  • VS Code editor

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗