›_ Codex Issues
Codex Issues / #30414

Incorrect BiDi (RTL/LTR) Text Rendering in Codex Chat Panel on VS Code

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

What version of the IDE extension are you using?

26.623.42026

What subscription do you have?

PLuse

Which IDE are you using?

VS Code

What platform is your computer?

_No response_

What issue are you seeing?

Bug: Incorrect BiDi (RTL/LTR) Text Rendering in Codex Chat Panel on VS Code
Summary

The Codex extension incorrectly renders mixed Persian (RTL) and English/code (LTR) text in both the chat input and chat output. The visual order of text becomes incorrect, making mixed-language conversations difficult to read.

Environment
Extension: Codex – OpenAI's coding agent
Extension ID: openai.chatgpt
Extension Version: 26.623.42026
VS Code Version: 1.125.1
OS: Windows 10 x64 (Build 19045)
Steps to Reproduce
Open the Codex chat panel.
Type or receive a message containing both Persian and English/code.

Example:

مهم سالم است build خواهش می‌کنم.

or

سلام build دنیا
Expected Behavior

The Persian text should remain right-to-left while English words and inline code should preserve their left-to-right direction without changing the surrounding sentence order.

Actual Behavior

The visual order becomes incorrect. English words or inline code cause adjacent Persian text to be reordered, making the sentence difficult to read.

The issue occurs in:

✅ Chat input box
✅ Assistant responses
Notes

This appears to be a Unicode Bidirectional (BiDi) rendering issue in the chat UI/WebView rather than a font problem.

The same Persian text displays correctly in the VS Code editor, suggesting the issue is specific to the Codex chat interface.

Additional Information

This issue is reproducible consistently on the latest versions of both VS Code and the Codex extension.

What steps can reproduce the bug?

just writing or replying

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 2 months ago

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

  • #30129

Powered by Codex Action

ahmadipiralvan · 1 month ago

Native Persian RTL/BiDi support is still missing in ChatGPT Windows and the Codex VS Code extension

I am a paying Persian-speaking ChatGPT and Codex user. Proper right-to-left support has been repeatedly requested for a long time, but Persian text is still rendered incorrectly in both the ChatGPT Windows application and the Codex VS Code extension.

This is not merely a text-alignment issue. It is a bidirectional-text rendering problem.

Current problems

  • Persian messages are not consistently rendered right-to-left.
  • Mixed Persian and English text appears in the wrong visual order.
  • Inline code, filenames, paths, commands, numbers, and punctuation reorder adjacent Persian words.
  • The input composer and assistant responses behave inconsistently.
  • Third-party RTL extensions that previously worked are no longer compatible with recent Codex extension versions.
  • Users are forced to downgrade Codex or modify application files manually.

Expected implementation

Please implement native RTL and BiDi support in both ChatGPT and Codex:

  • Use dir="auto" for message containers and the message composer.
  • Apply unicode-bidi: plaintext to natural-language message content.
  • Isolate code, commands, URLs, filenames, and paths with dir="ltr" and unicode-bidi: isolate.
  • Provide an interface setting with Automatic, Right-to-left, and Left-to-right options.
  • Add regression tests for mixed Persian/Arabic/Hebrew and English/code content.
  • Ensure Markdown lists, tables, punctuation, inline code, code blocks, and copy buttons work correctly in RTL messages.

Impact

This issue makes long technical conversations extremely difficult to read and significantly reduces the usability of ChatGPT and Codex for millions of Persian, Arabic, Hebrew, and Urdu users.

Accessibility and internationalization should not depend on unsupported third-party patches. Please treat native RTL/BiDi support as a product bug and accessibility requirement rather than an optional cosmetic feature.