[BUG] Left/Right arrow key history navigation causes unrecoverable loss of in-progress work

Status Open
Reported on v2.1.220
Maintainer reply None cached
Activity 0 comments · opened Aug 3, 2026

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?

While Claude Code is actively working (mid-task, streaming output), pressing the Left arrow key opens the conversation/chat history list view. Pressing Right arrow to return to the current session does nothing. Pressing Left arrow again causes Claude Code to jump back to an earlier point in the conversation, discarding all progress made since then — the previously sent message reappears, and Claude responds as if the intervening work never happened.

This has happened multiple times during active development sessions, each time resulting in significant lost work. It's especially easy to trigger accidentally since arrow keys are commonly used during normal terminal interaction.

Possibly related to #80726 (same left-arrow history/guard feature area), but that issue is about the confirmation being silently ignored, whereas this one results in actual state rollback and data loss.

What Should Happen?

Right arrow (or Esc) should safely return to the current/latest session without any state change. If arrow-key history navigation is intentional, it should not silently roll back and discard uncommitted in-progress work — at minimum there should be a confirmation prompt before reverting.

Error Messages/Logs

Steps to Reproduce

  1. While Claude Code is actively working (mid-task, streaming output), press the Left arrow key.
  2. This opens the conversation/chat history list view.
  3. Press Right arrow to return to the current session — nothing happens.
  4. Press Left arrow again.
  5. Claude Code jumps back to an earlier point in the conversation, discarding all progress made since then. The previously sent message reappears, and Claude responds as if the intervening work never happened.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.220

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_

View original on GitHub ↗