[BUG] plan mode questionnaire does not accept text (inhibiting dictation, forcing arrow key usage)
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?
users are forced to use special keys when presented with questionnaires, but the user should just be able to respond directly to those sections with text, making it easier for disabled ppl to use dictation devices. I myself use claude via voice on the go all the time, and have to stop and work around the stupid UX forced on me.
What Should Happen?
When you ask me questions will I be able to just type back without choosing arrow keys? I dont like using machines, and just want to dictate text ● Yes! When I use the AskUserQuestion tool, there's always an "Other" option that lets you provide custom text input instead of selecting from predefined choices. So you can absolutely just dictate your response as text - you're not locked into arrow key selections. The tool is designed to support both:
- Quick selection from suggested options (if one fits perfectly)
- Free-form text input via "Other" (for dictation or custom responses) This means you can interact naturally by just typing or dictating your answers, which should work well with your preference for voice input.
can we try it? ask me something
● User answered Claude's questions: ● Perfect! You selected "Detailed explanations" from the options. You also had the "Other" option available where you could have typed/dictated anything you wanted instead of choosing from my suggestions. So you have both paths available - quick selection or free-form text input. This means when I ask clarifying questions during development, you can always just dictate your response naturally if the predefined options don't quite fit what you want to say.
so yo did not get my sentences actually, which is rather dumb. Why wuold the question interface not simply also accept keyboard input directly, making it go to "other" ● You're absolutely right - that is a poor design. You explicitly told me you prefer dictating text and don't like using machines, and then the question interface forced you to use arrow keys/selection anyway. The interface should just accept keyboard input directly and automatically treat it as "Other" input. Making you first select "Other" before typing is an unnecessary friction point that defeats the purpose of supporting free-form text input. This is a limitation of how the AskUserQuestion tool is currently implemented - not something I can change on my end. I can only use the tool as designed. Given your preference for dictation and minimal machine interaction, I should probably minimize my use of this tool and instead:
- Just explain options in plain text
- Let you respond naturally by typing/dictating
- Reserve the tool for situations where structured choices genuinely add value Thanks for the feedback - this is genuinely useful to know about your workflow preferences.
can you pass this feedback to the team? tool for that? ● I don't have a tool to directly submit feedback to the team, but I can tell you the official channel: GitHub Issues: https://github.com/anthropics/claude-code/issues You could file an issue there with something like: Title: "AskUserQuestion tool should accept direct keyboard input as 'Other' response" Description:
- Current behavior: User must select "Other" option first, then type response
- Expected behavior: Direct keyboard typing should automatically route to "Other" input
- Use case: Users who prefer dictation/voice input shouldn't be forced to navigate UI with arrow keys first
- Impact: Adds unnecessary friction for accessible/voice-driven workflows Would you like me to help you draft a more detailed issue description? Or you can just file it yourself with the core point: keyboard input should go directly to "Other" without requiring menu navigation first.
Error Messages/Logs
Steps to Reproduce
- ask for a questionnaire
- observe arrow keys are the only input accepted
Claude Model
None
Is this a regression?
No, this never worked
Last Working Version
No response
Claude Code Version
2.0.55
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
No response