[BUG] Hebrew (RTL) text displays incorrectly in VSCode chat panel

Resolved 💬 3 comments Opened Mar 2, 2026 by maya5768 Closed Mar 6, 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?

Bug description:
Hebrew text in the Claude Code VSCode extension chat panel
renders LTR instead of RTL, making it unreadable.

Actual behavior:
Hebrew text displays left-to-right (LTR), characters appear
reversed and jumbled.

Suggested fix:
Add unicode-bidi: plaintext to the chat message CSS,
which auto-detects direction per paragraph.

Environment:

  • VSCode on Windows
  • Claude Code extension

What Should Happen?

Expected behavior:
Hebrew text should display right-to-left (RTL

Error Messages/Logs

Steps to Reproduce

  1. Open VSCode with Claude Code extension installed
  2. Start a conversation in Hebrew (RTL language)
  3. Claude responds in Hebrew
  4. Observe that Hebrew text appears reversed/jumbled (LTR instead of RTL)

Environment:

  • OS: Windows
  • VSCode version: latest
  • Claude Code extension: latest

Suggested fix:
Add unicode-bidi: plaintext to the chat message CSS container.
This auto-detects text direction per paragraph without breaking English/code display.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.63

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

The bug is in the VSCode extension chat panel UI, not in the CLI.
Hebrew (RTL) text responses appear left-to-right, making them unreadable.
The fix should be adding unicode-bidi: plaintext to the chat CSS.

<img width="1911" height="990" alt="Image" src="https://github.com/user-attachments/assets/e6204f26-1699-4096-a022-3065c8b5d5ca" />

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗