AskUserQuestion: "Other" text field content remains after submission
Status Fixed / completed
Maintainer reply ✓ Yes — bcherny
Activity 4 comments · opened Jul 10, 2026 · closed Aug 17, 2026
💡 Likely answer: A maintainer (bcherny, collaborator)
responded on this thread — see the highlighted reply below.
Description
After submitting an AskUserQuestion with the "Other" (free-text) option, the text entered by the user remains visible in the textarea even after the response is confirmed.
Steps to reproduce
- Trigger an
AskUserQuestionwith at least one question - Select "Other" and type custom text
- Submit the response
- Observe that the typed text remains in the textarea after submission
Expected behavior
The textarea should be cleared (or the entire widget dismissed) after submission.
Environment
- Claude Code (latest)
- Reported: 2026-07-10
Showing cached comments. Read the full discussion on GitHub ↗
3 Comments
Thanks for the report. I tried to reproduce this on 2.1.233 in a terminal on Linux.
I ran several question prompts and answered each one through the free-text ("Other") option: a single question, two questions in one prompt, and a multi-select question, plus a second question later in the same session. In every case the question widget was dismissed on submit and replaced by the answer summary, the input line was empty afterwards, and the free-text field of any following question started empty. So I can't reproduce it as described on the current terminal build.
Your wording ("textarea") makes me suspect this was on a non-terminal surface. To narrow it down, could you share:
claude --version) and OS, plus terminal emulator if it was the terminalclaude doctorA screenshot or short recording of the state right after submitting would help a lot too.
🤖 Generated with Claude Code
We weren't able to reproduce this. Could you provide steps to trigger the issue — what you ran, what happened, and what you expected? This issue will be closed automatically if there's no activity within 7 days.
Thanks for looking into this!
I tried to reproduce it just now but couldn't.
It seems to have been fixed in a recent update. Feel free to close this issue.