[BUG] Backslash Input via Option + ¥ Outputs Yen Symbol in PyCharm Terminal (Mac Japanese Keyboard)
Environment
- Platform (select one):
- [x] Anthropic API
- [ ] AWS Bedrock
- [ ] Google Vertex AI
- [ ] Other:
- Claude CLI version: <!-- output of
claude --version--> 1.0.16 - Operating System: Mac OS Sonoma 14.7.1
- Terminal: Pycharm 2025.1.1.1
Bug Description
When attempting to enter a backslash (\) using the standard Japanese Mac keyboard shortcut (Option + ¥), the terminal instead outputs a yen symbol (¥). This prevents the proper input of backslashes required in command-line operations.
Steps to Reproduce
- Run Claude Code in the Pycharm terminal
- Try to enter a backslash using Option + ¥ (standard shortcut on Japanese Mac keyboards)
Expected Behavior
Pressing Option + ¥ should insert a backslash (\)
Actual Behavior
Pressing Option + ¥ inserts a yen symbol (¥)
Additional Context
- This issue does not occur in the default macOS Terminal app. The same key combination correctly inputs a backslash (\) there.
- This issue also does not occur in PhpStorm (2024.1.3) — another JetBrains product. In PhpStorm’s terminal, Option + ¥ correctly results in a backslash.
- The problem appears to be specific to PyCharm’s built-in terminal, suggesting an inconsistency across JetBrains IDEs.
I am also having the same issue 😭
hey @MiuraKeiya and @MiuraToya! Thanks for the report.
This is caused by a conflict in the key mapping Option+Enter for new lines. Can you please turn off the Option+Enter settings with the 2 toggles below?
-
Settings > Tools > Claude Code [Beta]-> UncheckEnable using Option+Enter for multi-line prompts -
Settings > Tools > Terminal-> UncheckUse Option as Meta key
After that you should be able to use Option key as before. Unfortunately, this means you won't be able to use Option+Enter to enter new lines. You can try using Shift+Enter for new lines (it's an experimental feature, which may or may not work depending on which type of terminal is running).
Please let me know if you encounter any other problems!
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.
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.