[BUG] Word deletion doesn't work with non-latin alphabet
Status Fixed / completed
Maintainer reply None cached
Activity 12 comments · opened Jun 11, 2025 · closed Dec 10, 2025
Environment
- Platform (select one):
- [x] Anthropic API
- [ ] AWS Bedrock
- [ ] Google Vertex AI
- [x] Other: Max Account
- Claude CLI version: 1.0.18 (Claude Code)
- Operating System: macOS 15.5
- Terminal: Tested in multiple terminals: Ghostty, vscode terminal, iTerm2, Terminal app
Bug Description
When text in Claude Code contains non-latin characters, word deletion (opt + delete) deletes the whole text, not just the word. If there is a mixture of non-latin and latin characters, the non-latin text will be deleted up to the first latin symbol.
The same issue occurs with word navigation (opt + ← / opt + →).
Steps to Reproduce
- Type text using only non-latin characters (e.g., 'тестовый текст на русском языке'). I've tested with Cyrillic and Thai characters.
- Navigate to the end of the text.
- Press opt + delete.
Expected Behavior
Only the last word should be deleted.
Actual Behavior
The entire text is deleted.
Additional Context
https://github.com/user-attachments/assets/2e1ecb58-9f77-4b20-9b79-317bc5129203
12 Comments
ticket metioned above is a similar case, but for Windows with Ctrl+arrow
The problem still exists
@anthropic when fix?
I can confirm this issue on macOS in PyCharm’s integrated terminal using
claude-codeThe problem still exists in Claude 2.0.1
@anthropics when fix? 🤔
It seems like nobody uses anything other than English in @anthropics
Fixed in 2.0.67 🎉
Yes, at last! It was very annoying. I spent a lot of time typing the same thing that I had removed by accident.
Thank you, @cirospaciari
@Kolger Off topic: For future reference, you didn't have to type the same thing again! You can either press
Ctrl+-to undo the previous action, e.g. deletion, orCtrl+Yto paste from the kill ring. Might save you some time if it happens again!@Perlence Thank you, didn't know this one :) I've been using ctrl+g to open external editor for a while to avoid this.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.