[BUG] CLaude code Shows (RTL) and mixed-language content in corrupted way

Status Open
Reported on v2.1.92
Maintainer reply None cached
Activity 6 comments · opened Apr 15, 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?

The Claude Code CLI fails to properly render or handle Arabic text (Right-to-Left/RTL). When the output contains Arabic characters—or a mix of English and Arabic—the text becomes fragmented, incorrectly aligned, or rendered in reverse. This makes it extremely difficult to read code suggestions, logs, or chat responses, significantly hindering the utility of the tool for Arabic-speaking developers.

What Should Happen?

Claude Code should support bidirectional text (BiDi) in the terminal, correctly displaying Arabic characters and maintaining the integrity of mixed-language (English/Arabic) content. The text should be readable, correctly aligned, and properly formatted without character corruption or layout breaks.
that contains the input fields, the user writes his/her message in it, and the AI response

Error Messages/Logs

N/A (This is a rendering/display issue, not a crash error).

Steps to Reproduce

Steps to Reproduce*

Open your terminal and start Claude.

Ask Claude to explain a concept in Arabic or provide a comment/variable name in Arabic.
like "اشرح مفهوم ال evenets في هندسة البرمجيات وما المفاهيم المرتبطة به "

Observe the output in the terminal.

The Arabic text will appear jumbled or mirrored (e.g., words appearing in reverse order or separated characters).

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.92

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_

View original on GitHub ↗

6 Comments

MeiravGit · 4 months ago

I’m joining this request! this is extremely critical.

aeongenics · 4 months ago

So many people suffering from this! Pls fix this! Not just arabic but Hebrew too

RedaWork · 3 months ago

we still waiting for fix

codedatamine · 2 months ago

Title: Arabic (RTL) text rendering is broken in chat output and AskUserQuestion dialog

Environment:

  • Claude Code VS Code extension
  • VS Code version
  • OS: Windows 10

Description:
Arabic text rendered in the assistant's chat responses and in the
AskUserQuestion popup is hard to read. The container appears to use a
left-to-right (LTR) base direction, so when Arabic text is mixed with
Latin words, numbers, parentheses, or arrows (→), the Unicode
bidirectional (BiDi) algorithm reorders tokens incorrectly. Words and
punctuation jump to the wrong positions, making the text confusing for
native Arabic readers.

Expected behavior:
Each block/paragraph should set dir="auto" (or detect the first strong
character) so that Arabic paragraphs render right-to-left and embedded
Latin runs are isolated correctly. This applies to:

  1. The markdown chat output panel.
  2. The AskUserQuestion options dialog (question text, option labels,

and descriptions).

Suggested fix:
Add dir="auto" to the rendered markdown containers and to the
AskUserQuestion text elements, or wrap mixed content using Unicode
isolate characters (FSI/PDI).

Screenshots:

<img width="678" height="318" alt="Image" src="https://github.com/user-attachments/assets/a09cb356-cfa3-4d33-8101-c5497ad6c553" />

berrebioron-ops · 2 months ago

+1 — Confirming this bug also affects Hebrew (RTL) on macOS, not just Arabic on Windows. This is a cross-platform,
cross-language issue affecting all RTL-script users.

My setup:

  • macOS (Darwin 25.5.0)
  • Claude Code latest version
  • Hebrew as primary working language

Impact:
I'm a non-developer using Claude Code daily to manage several personal Flask projects. Every single response from
Claude is in Hebrew, and the RTL rendering bug makes the output nearly unreadable:

  • Hebrew sentences flip direction when mixed with any English word, file path, function name, or punctuation like

://

  • Terminal commands embedded in Hebrew text become jumbled
  • Even periods (.) inside a Hebrew sentence can flip the entire line
  • I've had to instruct Claude to never mix Hebrew with English on the same line — but this is a workaround for a real

terminal rendering bug, not a solution

Workaround I'm forced to use:
I maintain a strict personal rule in my CLAUDE.md telling Claude to:

  • Never mix Hebrew and Latin characters on the same line
  • Always isolate technical terms (commands, file paths, function names) in separate code blocks
  • Write tool/website names in Hebrew transliteration (גיטהאב instead of GitHub)

This works around the symptom but means I cannot use Claude Code's normal mixed-language output capabilities at all.

Severity:
For RTL-language users this is not a minor UI polish issue — it's a blocker. The product is essentially unusable in
its native rendering mode. The area:a11y label is correct: this is an accessibility barrier for an entire linguistic
community (Arabic, Hebrew, Persian, Urdu speakers — hundreds of millions of users).

Request:

  1. Could the Anthropic team provide a status update or ETA for a fix?
  2. Given that this is a known accessibility bug affecting paying Max subscribers, I'd like to formally request that

affected users be compensated (subscription credit, extended Pro/Max time, or equivalent) for the months during which
the product has been partially unusable for them.

Original issue I filed: #68608 (closed as duplicate, redirected here)

Thank you for your attention.

Har2yQn78 · 1 month ago

For anyone hitting this — I built rtlwrap, a small wrapper that fixes RTL/Arabic/Persian/Hebrew rendering for any terminal program, including Claude Code's full-screen UI. No patches to Claude Code or your terminal needed:
rtlwrap claude
It works by running the program on a PTY and reshaping text in transit. Might not be the "official" fix this issue is asking for, but it solves the immediate pain today. Happy to take feedback if anyone tries it.