AskUserQuestion: text typed in "Other" free-text field is invisible until focus moves to Submit
Resolved 💬 6 comments Opened Apr 20, 2026 by mikhailgrinberg Closed Jun 14, 2026
Environment
- Claude Code version: 2.1.114
- OS: macOS 26.3.1
- Terminal: iTerm2 3.6.9 (not confirmed terminal-specific — only observed here)
- Shell: zsh
Description
When the AskUserQuestion tool presents a free-text "Other" / open-answer option, typing into it works functionally (input is captured and submitted correctly), but the typed text is not rendered in the input area while typing. It sits in a visual blind spot.
Moving focus to the "Submit" row causes the previously-typed text to appear.
This seems to be a regression — behavior started after a recent Claude Code update (observed April 2026).
Steps to reproduce
- In a Claude Code session, trigger an AskUserQuestion prompt that includes a free-text "Other" option.
- Navigate to the "Other" option and type a response.
- Observe: keystrokes are accepted but the input area does not update visibly. The option row may also appear truncated (e.g. "5.[✓] Todos: send him a summar…").
- Tab/arrow down to "Submit" — the typed text now becomes visible.
- Submitting works correctly; the full text is sent.
Expected
Typed characters appear live in the input area as the user types.
Actual
Input is invisible while typing. Text only renders after focus leaves the field (e.g. moving to Submit).
Notes
- Possibly related to #50932 (unified interactive gate feature request) and #10848 (closed as duplicate — multi-line not shown while typing). This may be the same underlying issue as #10848 but still present in 2.1.114.
- Screenshot available (will attach via web UI after filing).
This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗