Vouch request: configurable Escape-clears-input behavior (escapeClearBehavior)

[xaviergmail]

Hi maintainers — per CONTRIBUTING I am opening a Discussion before a PR and requesting a vouch (!vouch @xaviergmail).

What I would like to contribute

A small, opt-in TUI quality-of-life setting. Today single-Escape on a non-empty draft unconditionally clears the composer with no way to recover the text. As a vim user I reflexively hit Escape mid-prompt and lose long drafts.

Proposed: a new escapeClearBehavior setting, default discard (current behavior, byte-for-byte), plus two opt-in modes:

• discard — clear the draft (unchanged default)
• history — save the draft to prompt history first (Up Arrow restores it), then clear — via the existing CustomEditor.clearDraft(text)
• none — leave the draft untouched; Ctrl+C still clears

Both idle-clear sites in InputController.onEscape (main view and focused-subagent view) honor the setting. For none at the main site the Escape is still consumed (double-Esc timer + streaming-escape arm reset) so a no-op Esc cannot seed a spurious /tree|/branch backtrack. Bash/python mode-exit clears are untouched.

Scope

6 files, +145/-3:

• packages/coding-agent/src/config/settings-schema.ts — new enum setting
• packages/coding-agent/src/modes/controllers/input-controller.ts — gate both clear sites
• docs/settings.md, docs/keybindings.md — documented
• packages/coding-agent/CHANGELOG.md — ### Added entry
• packages/coding-agent/test/input-controller-escape.test.ts — +5 tests (all 3 behaviors at both sites)

Verified locally: bun test input-controller-escape.test.ts → 35 pass / 0 fail; check:types clean; biome check clean.

Branch is ready on my fork: https://github.com/xaviergmail/oh-my-pi/tree/feat/configurable-escape-clear-input

Happy to adjust the naming/defaults/approach to your preference before I open the PR. Thanks!

[can1357]

!vouch @xaviergmail
sounds good!