[BUG] Unusable crashes since v2.0.50

[apolopena]

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?

I'm pretty sure everyone's aware of this. Any writes to large files pretty much crash the system. Time taken stops ticking, tokens stop ticking, and you never know if the job is going to complete or not. I can't get any work done without reverting to v2.0.49 and disabling auto updates.

Anthropic needs to formally acknowledge this. I'm not sure how anybody's getting any work done with any version of Claude Code past V2.0.49

What Should Happen?

The harness should not crash. People that pay for the service should be able to get work done with the latest versions. Engineers should not introduce major breaking bugs without formal damage control.

Error Messages/Logs

Steps to Reproduce

1. Make substantial edits to a large file.
2. Watch it crash.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

v2.0.49

Claude Code Version

v2.0.50, v2.0.52, v2.0.52, v2.0.53, v2.0.54, v2.0.55

Platform

Anthropic API

Operating System

Other

Terminal/Shell

VS Code integrated terminal

Additional Information

No response

[github-actions[bot]]

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/12138
2. https://github.com/anthropics/claude-code/issues/12237
3. https://github.com/anthropics/claude-code/issues/12222

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

[apolopena]

A bug of this magnitude that's persisted across five versions needs formal damage control from the company that released it. Therefore, I do not consider this to be a duplicate bug.

[0xinf0]

This tool has become unusable. It is now officially broken. What a shame for such a large team. It's great for small little tasks, anything serious and long term, you are on your own. I am having to recover from a 100% frozen state almost every hour now. so frustrating.

[apolopena]

Initial tests show this may have been resolved in v 2.0.56. More to follow.

[bencoopertx]

The extension crashes very frequently in both VSCode and Cursor. Best option as of right now has been to reopen and start the chats until they crash again as the versions that crash less don't support Opus.

[apolopena]

This bug is not regarding an IDE extension. I belive it was mostly addressed since v 2.0.56

[github-actions[bot]]

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.