Up arrow key destroys composed message in input
Resolved 💬 3 comments Opened Apr 13, 2026 by miadisabelle Closed Apr 17, 2026
Summary
Pressing the up arrow key while composing a multi-line message in the input field replaces the entire composed text with the previous message from history. No confirmation, no undo. The work is gone.
Steps to Reproduce
- Start composing a long, multi-line message in the Claude Code CLI input
- Accidentally press the up arrow key
- The entire composed message is replaced by the previous history entry
- No way to recover the lost text
Expected Behavior
Either:
- Up arrow should not replace text while mid-composition (only activate history navigation when input is empty)
- Or provide an undo mechanism (e.g., down arrow restores the draft)
Impact
Loss of significant user work mid-thought. Particularly painful for detailed, multi-paragraph prompts that take time to compose.
Environment
- Platform: Linux
- Shell: bash
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗