Summary: The TUI multi-select UserInputView has a control-flow trap: pressing Enter on a real option toggles it (crates/tui/src/tui/user_input.rs:252-263), matching single-select Enter which submits (line 266). A user who presses Enter twice on the highlighted option (the natural "select & confirm" gesture) un-ticks it, and the Confirm row then submits an empty answer set, which the code explicitly allows ("skip-like", line 247-250). The question advances with no answer and the model's intended default is never consulted.
When hit: any request_user_input multi-select prompt (e.g. "which scopes?") where the user double-presses Enter on an option.
Impact: incorrect/empty answers submitted mid-turn; behavior contradicts the single-select path on the same view.
Repro: multi-select with 2 options; press Enter on option 1 twice, then Enter on Confirm → answers = [].
Found in a read-only v0.9.4 bug hunt (2026-08-02).
Summary: The TUI multi-select
UserInputViewhas a control-flow trap: pressing Enter on a real option toggles it (crates/tui/src/tui/user_input.rs:252-263), matching single-select Enter which submits (line 266). A user who presses Enter twice on the highlighted option (the natural "select & confirm" gesture) un-ticks it, and the Confirm row then submits an empty answer set, which the code explicitly allows ("skip-like", line 247-250). The question advances with no answer and the model's intended default is never consulted.When hit: any
request_user_inputmulti-select prompt (e.g. "which scopes?") where the user double-presses Enter on an option.Impact: incorrect/empty answers submitted mid-turn; behavior contradicts the single-select path on the same view.
Repro: multi-select with 2 options; press Enter on option 1 twice, then Enter on Confirm → answers = [].
Found in a read-only v0.9.4 bug hunt (2026-08-02).