Hey, thanks for the detailed report and for both examples, the analysis is spot on.
You read the behavior correctly. Your own messages take direction from the first strong character in each paragraph, so a sentence that starts with an English identifier like createFormClient flips the whole line to left-to-right. Assistant replies don’t detect direction yet, so a Persian sentence with an English token in the middle gets laid out as LTR, and the word order and punctuation look scrambled. The text itself is still intact, if you copy it into an RTL-aware editor, it reads correctly. This is a chat rendering limitation, not a model issue.
This is a known issue we’re tracking, and I’ve added your report to it. We don’t have a complete fix in the app yet, and I can’t share an exact timeline. I’ll post in the thread when there’s an update.
For now, two things help:
- Ask the model to put Persian and English on separate lines, or keep names in inline code, this avoids most of the reordering.
- Some folks in the community maintain extensions that apply RTL styling to the chat panel, for example the one shared in this thread: Add RTL for chat
Let me know if the workaround doesn’t help.