AskUserQuestion free-text input: text scrolls out of view past the first line; ctrl+g 'edit in Notepad' doesn't return (Windows ConPTY)

Open 💬 0 comments Opened Jun 14, 2026 by mikejsmith1985

Environment

  • Claude Code with model Opus 4.8 (claude-opus-4-8)
  • Windows 11 Pro (26200)
  • Running inside a ConPTY host (Forge Terminal, xterm.js front-end). Normal prompt input wraps correctly in the same terminal, so the host's PTY width is reported correctly.

Issue 1 — free-text answer input doesn't stay visible past line 1

When answering an AskUserQuestion prompt via the free-text 'Other' field, typing up to the right edge of the first line causes the entered text to disappear from view — the input neither wraps to a second visible line nor horizontally scrolls to keep the cursor/typed text on screen. You're typing blind past column ~1 line.

Expected: the input wraps or horizontally scrolls so typed text and cursor stay visible.

Issue 2 — ctrl+g 'edit in Notepad' does not return to the prompt

The footer offers ctrl+g to edit in Notepad. Invoking it does not return control to the question prompt afterward — the session appears stuck and the answer can't be completed.

Expected: after closing the external editor, the edited answer is returned to the prompt and selection/submission continues.

Repro

  1. On Windows, run Claude Code inside a ConPTY-based terminal host.
  2. Trigger an AskUserQuestion prompt and choose the free-text 'Other' option.
  3. Type past the first visible line → text scrolls out of view.
  4. Alternatively press ctrl+g → Notepad path does not return to the prompt.

Notes

The question UI is rendered by Claude Code (the strings 'Tab/Arrow keys to navigate', 'edit in Notepad', 'Esc to cancel' are emitted by the CLI). The hosting terminal renders normal wrapped output and prompt input correctly, which points at the picker's own inline-input rendering / external-editor handoff rather than the host.

View original on GitHub ↗