[BUG] After compaction the terminal resets and i cannot scroll up and see what all were discussed, changed and done.

Status Closed — duplicate
Maintainer reply ✓ Yes — claude[bot]
Activity 12 comments · opened Dec 9, 2025 · closed May 2, 2026
💡 Likely answer: A maintainer (claude[bot], contributor) responded on this thread — see the highlighted reply below.

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?

During the claude running sessions, claude initiates the compaction and after the compaction, the entire terminal is reset and then we cannot scroll up and check what all we discussed in the session, which all files were modified. Basically all history of the conversation is lost.

What Should Happen?

The terminal should not reset on compaction and we should be able to see the history of the commands and conversation.

Error Messages/Logs

On compaction, my terminal is reset and all my history of commands is lost and i see the claude symbol and none of my previous conversation/commands.

Steps to Reproduce

Just keep on interacting with claude and once the terminal is reset check if all the context and conversation and the details of changes done, files updated etc are lost.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Claude Code v2.0.59

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

12 Comments

github-actions[bot] · 8 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/8828
  2. https://github.com/anthropics/claude-code/issues/13308
  3. https://github.com/anthropics/claude-code/issues/9001

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

george-pc · 8 months ago

Claude compaction is resetting the terminal and all previous history in the terminal is lost and we cannot scroll and check.

github-actions[bot] · 7 months ago

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

george-pc · 7 months ago

The terminal is reset and all commands executed and history is lost, why do u need to reset the terminal on compaction as i might want to scroll up and see the history or the command used etc.

adrianroe · 7 months ago

Just to echo the above - it is very frustrating to have commands and prompts no longer available in the terminal scrollback. Claude needs to compact its context - that's fine. Why it needs to simultaneously delete terminal history I don't see.

kalyan02 · 6 months ago

+1 on this

scapeshift-ojones · 6 months ago

This is still unresolved as of v2.1.47. After compaction the terminal resets and there's no way to review what was discussed or changed. The "ctrl+o for history" banner is misleading — it enters transcript mode which only shows post-compaction content.

Consolidated into #27242 with JSONL-level evidence that the data is fully preserved — this is a UI gap, not a data loss issue. If you're still hitting this, please 👍 and comment on #27242 to help push it past the triage threshold.

s-smits · 6 months ago

Bump

scapeshift-ojones · 6 months ago

@s-smits Still broken on v2.1.50 — no fix in any recent release. This is now tracked in the consolidated issue at #27242 alongside branch navigation regression and plan-mode context loss. If you haven't already, please 👍 and comment there to help push past the triage threshold. Combined engagement across 13 related issues is 118+ thumbs-up but it's fragmented — consolidating on #27242 is the best path to getting this fixed.

claude[bot] contributor · 4 months ago

This is a duplicate of #34718, which was fixed as of version v2.1.101.

george-pc · 3 months ago

This issue was raised on Dec 9, 2025
The one u say as duplicate was on a later date on Mar 16

So how are u closing this as a duplicate of a later date issue ?

github-actions[bot] · 2 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.