Full-width digits (1-9) don't select options in the question dialog

Status Open
Reported on v2.1.220
Maintainer reply None cached
Activity 2 comments · opened Aug 2, 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 Claude asks a question and shows a numbered list of options, pressing an ASCII digit (1-9) selects the corresponding option. Pressing the full-width equivalent (-, U+FF11–U+FF19) does nothing at all.

This matters for Japanese users: with a Japanese input source active, digits are often emitted as full-width characters, so the number shortcut silently stops working and you have to fall back to arrow keys.

What Should Happen?

Full-width digits U+FF10–U+FF19 select options exactly like their ASCII counterparts, consistent with the rest of the TUI.

Error Messages/Logs

Steps to Reproduce

  1. On macOS, switch the input source to Japanese and put it in full-width alphanumeric mode. (Any input path that emits U+FF11 reproduces it, including pasting .)
  2. Ask Claude something that makes it present a question with numbered options.
  3. Press (full-width one) — nothing happens.
  4. Press 1 (ASCII one) — option 1 is selected.

Claude Model

_No response_

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.220 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Cursor

Additional Information

This looks like a missed spot rather than intended behavior, because full-width digits are already normalized elsewhere in the TUI:

  • the generic single-select and multi-select lists accept full-width digits
  • the Enter selection [1-N] numeric entry mode accepts them
  • within the same question dialog, the trailing "Submit" row responds to its full-width number

Only the option numbers 1-9 in the question dialog itself appear to be compared as raw ASCII, so they miss the conversion the surrounding code already applies.

Suggested fix: run the pressed key through the same full-width→half-width normalization helper the neighbouring handlers already use, before the digit comparison in the question dialog's key handler.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗