Left-arrow (←) triggers session/answer navigation during text editing — too easy to trigger accidentally, no confirmation

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Environment

• Claude Code: 2.1.197
• OS: Windows 11 (10.0.26200), PowerShell
• Terminal: (aizpildi — piem. Windows Terminal / VS Code integrated / cmd)

Summary
The Left arrow (←) key — which is a high-frequency key used constantly for cursor movement while typing and editing a prompt — also triggers a navigation/overlay behavior (session/answer stepping). Because it's the same key used for normal text editing, it is extremely easy to activate unintentionally, which is confusing and, in my case, led to ending up with duplicate/forked sessions for the same task.

Steps to reproduce

1. Be in the interactive prompt, editing/correcting a multi-line or longer message.
2. Use ← to move the cursor back through the text (normal editing).
3. Under the wrong input state, ← instead triggers navigation (stepping through previous answers / session context) rather than just moving the cursor.

Expected behavior

• ← should only move the cursor within the input line during normal text editing.
• Any "jump to previous session/answer/context" navigation should be bound to a less collision-prone key (e.g. a modifier chord like Ctrl+←, or PageUp/PageDown), and/or require a confirmation, since it changes context.

Actual behavior

• ← activates context/answer navigation while I intend to edit text. This is easy to hit by accident and produces confusion. It contributed to my having 2 near-identical duplicate session files for one task, which I only untangled by manually diffing the ~/.claude/projects/**.jsonl transcripts.

Impact

• A destructive-feeling context switch is bound to one of the most frequently pressed editing keys, with no confirmation and no obvious way to undo the surprise.

What Should Happen?

Suggestion

• Move this navigation off the bare ←/→ keys onto a modifier chord or a rarely-used key, and/or
• Add a small confirmation (or at least a visible, dismissible indicator) before switching context, and/or
• Make it clearly remappable via ~/.claude/keybindings.json.

Error Messages/Logs

Steps to Reproduce

Steps to reproduce

1. Be in the interactive prompt, editing/correcting a multi-line or longer message.
2. Use ← to move the cursor back through the text (normal editing).
3. Under the wrong input state, ← instead triggers navigation (stepping through previous answers / session context) rather than just moving the cursor.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Claude Code: 2.1.197

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_