Enhancement: Persist session memory/context on rate limit cutoff to prevent total loss of work

Problem

When a session hits a rate limit and is hard-cut off, all conversation context and in-progress work is completely lost. There is no mechanism to auto-save state, memory, or progress before the cutoff occurs. The next session starts completely blank.

This creates a deeply frustrating and costly user experience:

• The user paid for inference that produced real, valuable progress
• That progress is permanently lost with no recovery path
• The user must re-explain everything from scratch in the next session
• Claude has no memory of what it was doing, what files it created, what decisions were made, or where it stopped

Impact

For users

• Budget waste: inference was purchased and consumed, but the output is gone
• Time waste: re-briefing from scratch can take 30+ minutes
• Trust erosion: paying for a tool that silently discards your work is a fundamentally broken experience
• A reasonable analogy: imagine Amazon charged you for a shopping session, filled your cart, then wiped it overnight with no record

For Anthropic

• Compute waste: inference cycles that produced no durable value for the user
• Reputation damage: users who hit this experience don't come back
• Compounding problem: as adoption grows and rate limits tighten, this will affect more users more often

Proposed Solution

Before enforcing a rate limit hard cutoff, Claude Code should:

1. Auto-save a session summary to memory — capture what was being worked on, what decisions were made, what files were changed, and where it stopped
2. Write a checkpoint file to the project directory (e.g., .claude/session_checkpoint.md) summarizing in-progress state
3. Notify the user that a limit is approaching (soft warning) so they can manually save or wrap up
4. On next session start, detect the checkpoint and offer to resume from it

Even a plain-text summary of "here's what we were doing and where we stopped" would eliminate the majority of the pain.

Priority

This should be treated as high priority. Rate limits are a hard constraint that will only become more common as usage grows. The current behavior — silent context loss on cutoff — is one of the worst possible user experiences for a productivity tool.

Submitted via Claude Code by user bairdstar.