claude-code - 💡(How to fix) Fix AskUserQuestion: text typed in "Other" free-text field is invisible until focus moves to Submit

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

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).

Root Cause

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).

RAW_BUFFERClick to expand / collapse

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

  1. In a Claude Code session, trigger an AskUserQuestion prompt that includes a free-text "Other" option.
  2. Navigate to the "Other" option and type a response.
  3. 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…").
  4. Tab/arrow down to "Submit" — the typed text now becomes visible.
  5. 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).

extent analysis

TL;DR

The issue can be potentially resolved by investigating and addressing the regression introduced in the recent Claude Code update, possibly related to the unified interactive gate feature or multi-line input rendering.

Guidance

  • Review the changes introduced in the recent Claude Code update (version 2.1.114) to identify potential causes of the regression, focusing on the unified interactive gate feature and multi-line input rendering.
  • Investigate the relationship between this issue and the previously reported issues #50932 and #10848 to determine if they are related or if the fix for #10848 was incomplete.
  • Test the AskUserQuestion tool with different input types and scenarios to determine if the issue is specific to the "Other" option or if it affects other input fields as well.
  • Consider temporarily reverting to a previous version of Claude Code to verify if the issue is indeed caused by the recent update.

Example

No code snippet is provided as the issue does not specify any specific code-related details.

Notes

The issue may be specific to the combination of Claude Code version 2.1.114, macOS 26.3.1, and iTerm2 3.6.9, and may not occur in other environments. Further investigation is needed to determine the root cause and develop a comprehensive solution.

Recommendation

Apply workaround: Given the potential relationship with previous issues and the recent update, it may be necessary to wait for a fix or apply a temporary workaround, such as using a different terminal or shell, until the issue is fully resolved.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix AskUserQuestion: text typed in "Other" free-text field is invisible until focus moves to Submit