# Chat UI lacks RTL support — Persian is LTR-containered; mixed Persian+English BiDi is scrambled **URL:** \ **Category:** Bug Reports\ **Tags:** chat\ **Created:** [July 20, 2026, 5:21pm UTC](https://forum.cursor.com/t/chat-ui-lacks-rtl-support-persian-is-ltr-containered-mixed-persian-english-bidi-is-scrambled/166187 "2026-07-20T17:21:11Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [July 20, 2026, 6:09pm UTC](https://forum.cursor.com/t/chat-ui-lacks-rtl-support-persian-is-ltr-containered-mixed-persian-english-bidi-is-scrambled/166187/5 "2026-07-20T18:09:49Z")
Hey, thanks for the detailed report with examples, that’s really helpful. This is a known limitation: the Chat/Agent renderer doesn’t support RTL or Unicode BiDi isolation yet, so Persian content gets laid out as LTR, and lines that include English terms like PC, Online, EPS, etc. can look visually reordered even though the underlying text is correct. Direction should be handled at the UI layer, not by the model, you’re right. Full RTL/BiDi support in chat is on our radar, but I can’t share an exact timeline. It’s more complex than just `dir=auto` because we need to handle mixed RTL/LTR cleanly together with code blocks and markdown. This is already being discussed and collecting votes here, I’d recommend subscribing and adding your vote so we can better gauge demand: [Add RTL for chat](https://forum.cursor.com/t/add-rtl-for-chat/130110) If there’s an update, I’ll follow up. --- _[View the full topic](https://forum.cursor.com/t/chat-ui-lacks-rtl-support-persian-is-ltr-containered-mixed-persian-english-bidi-is-scrambled/166187)._