AskUserQuestion "Other" input field: long answers scroll off-screen with no way to view/edit

Summary

When a skill or plugin prompts for input via AskUserQuestion and the user selects Other to type a free-form answer, the input field is a single-line text box. Typing an answer longer than the visible field width causes the text to scroll horizontally — the beginning of the answer disappears off the left edge, and there is no way to view or edit anything that is no longer on-screen.

This is especially painful with skills that ask substantive open-ended questions (e.g. several compound-engineering skills: /ce-brainstorm, /ce-plan, /ce-ideate). Users frequently need to type a paragraph-length answer, and there is no usable way to do that inside the prompt.

Repro

1. Run any skill that calls AskUserQuestion with free-form-style options (e.g. /ce-brainstorm)
2. Choose Other
3. Type an answer longer than your terminal width (~120+ characters in a typical window)
4. Observe: the start of the answer scrolls out of view and cannot be brought back without deleting the tail. Arrow keys move the cursor but the viewport does not reveal more than one line at a time.

Environment

• Claude Code: @anthropic-ai/claude-code v2.1.144
• macOS 15.x, zsh
• Reproduces in Terminal.app, iTerm2, Ghostty — i.e. independent of terminal emulator

Expected

At minimum one of:

1. Word-wrap inside the field — let the input grow vertically into a multi-line region so the full answer is always visible.
2. Expand-to-editor keybinding — e.g. Ctrl+R or Ctrl+E opens the answer in $EDITOR (similar to how the main chat input handles long prompts with \ + Enter for multi-line).
3. Horizontal scroll indicators at the field edges so the user knows content exists off-screen, plus a key to jump cursor to start/end of input.

Option 1 (wrap) is the most discoverable. Option 2 (external editor) is the most useful for paragraph-length answers.

Why this matters

AskUserQuestion is the main interactive entry point for plugin authors — skills lean on it heavily. The current behavior pushes users to draft answers in a separate editor and paste them back in, which defeats the in-terminal UX the prompt is supposed to provide. The longer/more thoughtful the answer, the worse the experience.

Suggested fix direction

The prompt component appears to render as a single-line text input. Switching the Other option to render as a multi-line <textarea>-equivalent (auto-growing with line wrap) would address the dominant case. Single-select-from-list options can stay as they are.

Related Issues

• #46063 — AskUserQuestion 'Other' text input wraps too early on wide terminals. Almost certainly the same underlying TUI bug surfacing in the opposite direction: that report shows the input wrapping at ~75 columns on a 200-col terminal (wasted space), while this report shows the same fixed width forcing horizontal scroll on narrower terminals (lost visibility). A fix that respects actual terminal width plus enables vertical wrapping would resolve both.

Workarounds users currently rely on

• Resize terminal wider (only buys ~30-50 more characters)
• Type the answer in an external editor and paste it (loses the interactive flow)
• Avoid skills that use long-form prompts