This problem lives in the display layer: the terminal simply does not know how to render bidirectional text properly, and your agent actually wrote everything correctly. Three steps close most of the pain: a separate line for each language, a working environment that understands right-to-left, and one iron rule, never install a "fix" that swaps files inside the app itself.
My job on the team is to inspect every tool before it touches the system, which is why this question landed with me and not with our copywriter. First, the explanation: the model writes the text correctly. But when a sentence mixes Hebrew and English, the screen's bidirectional algorithm guesses where each run begins, and sometimes guesses backwards. In short, the limitation is built into the display. It is not a bug on your side (and not on the agent's side either, you can stop scolding it).
What works for us and for our graduates: move to the desktop app or to VS Code with an RTL extension instead of a bare terminal, teach the agent the line rule, every English term gets its own line or slides to the end of the sentence, and open every HTML output with a direction declaration. I counted this question dozens of times over six months in our community groups, and one member phrased the frustration perfectly: "asked a thousand times, still haven't found the perfect fix". Now there is one.
And the part that made this my column. A popular patch circulating in the community fixes the display by replacing files inside the Claude app. My translation: foreign code running with all of the app's permissions, seeing everything it sees, including your brain and your keys. Before installing anything like that, ask three questions: who wrote it, what exactly does it replace, and who read the code line by line. If all three come up empty, sore eyes are the cheaper price.
A prompt, on the house
Add the following rules to the system's main instruction file, under "Hebrew and display rules":
1. When you write in Hebrew, do not embed an English term mid-sentence.
An English term goes at the end of the sentence, or on its own separate line.
2. File names, commands and code snippets always sit on their own line or in a code block.
3. Every Hebrew HTML output opens with <html dir="rtl" lang="he">.
4. Never suggest installing an extension or patch that modifies another application's files.
If such a need comes up, stop and explain the risk to me first.Give it a week, and your eyes go back to reading instead of decoding.
