Back to blog
Context
Claude Code

Why does your resumed Claude Code session still lose recent turns?

Thắng Đoàn
Thắng Đoàn

If Claude Code crashes or is killed mid-session, resuming could silently drop your most recent turns, losing context you relied on. The current release fixes resumed sessions so recent turns survive an unclean exit.

What it is

Claude Code persists conversation state so a session can be resumed later. This release fixes a bug where recent turns sometimes went missing from a resumed session after Claude Code stopped without a clean exit.

Applied case

You leave a long Claude Code session running and your terminal or machine dies, so the process exits uncleanly. When you resume, you previously risked the newest turns vanishing, meaning Claude would forget your latest edits and instructions. After updating, resuming the same crashed session keeps those turns intact, so you continue where you left off instead of re-explaining. The same release also stops sessions on third-party gateways and Foundry from failing with a context length error every turn instead of compacting, a related context-loss pain.

  • Update before resuming a session that crashed, so recent turns are not dropped

When to use it

Use when you rely on resuming sessions after crashes, disconnects, or non-clean exits.
Skip when you always end sessions cleanly with exit and never resume old ones.

/rewind

Read more

Claude Code v2.1.325 release notes

Share:

Recommended for you

Enjoyed this article?

Subscribe for new articles. No spam. Unsubscribe anytime.

By subscribing you agree to receive the newsletter. No spam, and you can unsubscribe anytime.