[BUG] Claude Code terminal session lost conversation history after /resume

[samueltpark]

Preflight Checklist

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

What's Wrong?

The claude code session I was working in lost conversation history after resuming the session in a new terminal window.

What Should Happen?

Usually a session's conversation history does not disappear after closing and then resuming a session.

Error Messages/Logs

Steps to Reproduce

1. Spent a few hours working with claude code and then closed the terminal window.
2. Opened a new terminal window and used /resume
3. All of the session's conversation history from what I was working today was gone and the session picked up where I left off the day before.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.91

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

No response

[github-actions]

Found 3 possible duplicate issues:

1. Bug: --resume loads 0% context on v2.1.91 — three regressions in session loading pipeline (source code verified) #43044
2. [BUG] Session resume loses 80%+ of conversation — progress entries create parasitic forks in parentUuid chain #35024
3. [Bug] Conversation history lost after v2.1.90 update; context window and prompt suggestions malfunction #42877

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

[github-actions]

This issue has been automatically closed as a duplicate of #43044.

If this is incorrect, please re-open this issue or create a new one.

🤖 Generated with Claude Code

[github-actions]

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.