[AskUserQuestion] Two minor UX issues: Enter key doesn't submit "Other" field, response renders inside a code block

Resolved 💬 1 comment Opened Apr 30, 2026 by madmanu47 Closed May 31, 2026

Context

Using AskUserQuestion in interactive sessions. The format itself works well — clear options, descriptions, previews. Two small UX issues are worth flagging.

Issue 1 — Enter key inert in the "Other" text field

When the user picks "Other" and types a custom answer, pressing Enter inserts a newline (multi-line text area behavior). Submitting requires clicking the Submit button with the mouse, breaking keyboard flow for keyboard-driven users.

Expected: Enter submits, Shift+Enter (or similar) inserts newline — the common convention in chat UIs.

Issue 2 — Response renders as a code block in transcript

When re-reading the conversation, the captured answer appears inside a code-styled inline block, which is harder to read in flowing prose than plain text. A standard inline rendering would integrate better with the conversation history.

Optional — option numbering

Currently options must be manually prefixed with "1. ", "2. ", etc. in the label field for users to reference them by number when they pick "Other". An automatic UI-side numbering would remove this boilerplate from prompts.

Environment

  • Claude Code, native VSCode extension
  • Model: Claude Opus 4.7 (claude-opus-4-7)
  • OS: Windows 11

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗