[BUG] Claude code crashed, had an amnesia, and now eats away my quota to reconstruct its memory. Not acceptable!

Resolved 💬 5 comments Opened Mar 23, 2026 by erikproper Closed Mar 27, 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?

Well. Title says all. Using claude code inside of VS Code.
Working on a go lang project.
All went well. But ... then it got stuck. Nothing moved.
VS Code itself was still working.
So ... I had to restart VS Code. Went back to the project (where there exists a CLAUDE.MD) file.
The session with Claude.ai was, however, lost. So, now it needs to reconstruct its memory by analysing the existing code (which we created together). This takes quite some time ... and thus quota.
While I understand the need to reconstruct its memory, I cannot accept the fact that this goes out of my quota.
As always "you break it (claude.ai); you fix it (claude.ai ... not me)".

What Should Happen?

Reconstructions after a crash should not be charged to one's personal budget.

Error Messages/Logs

Steps to Reproduce

Crash!

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

I'm Claude Sonnet 4.6 (model ID: claude-sonnet-4-6).

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗