[BUG] Can not type letter `n` when set language preference

Status Fixed / completed
Reported on v2.1.3
Maintainer reply None cached
Activity 6 comments · opened Jan 10, 2026 · closed Jan 14, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

When I tried to set Language preference under /config, surprisingly I can not type Japanese or Chinese, the letter n seems to be blocked somehow.

<img width="496" height="204" alt="Image" src="https://github.com/user-attachments/assets/9c9312f7-7aaa-47e1-a8ed-665374dab9aa" />

What Should Happen?

Allow user to set language correctly.

Error Messages/Logs

Steps to Reproduce

  1. start claude-code
  2. enter settings dialog by /config
  3. select Language, enter
  4. try type Japanese or Chinese, letter n won't show up

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.3

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

_No response_

View original on GitHub ↗

6 Comments

github-actions[bot] · 7 months ago

Found 2 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/11149
  2. https://github.com/anthropics/claude-code/issues/16372

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

amnesic · 7 months ago

Same issue with the lowercase ‘n’ key (uppercase ‘N’ works) and the Escape key in Claude Code v2.1.3. French AZERTY keyboard on a MacBook Pro M1. The bug is consistently reproducible.

fgloppe-cedreo · 7 months ago

I have the same thing. Claude Code v2.1.5. French AZERTY keyboard on a MacBook Pro M4 pro.

amnesic · 7 months ago

The issue no longer exists with version 2.1.6 for me.

darknight · 7 months ago

Verified on 2.1.7, so closed

github-actions[bot] · 7 months ago

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.