claude-code - 💡(How to fix) Fix [BUG] Claude Code freezes during thinking or at a random token while still consuming usage limits [1 comments, 2 participants]

Claude Code should either complete the response or return a timeout/error and stop consuming limits. In its current state, this can be perceived as misleading for users. Claude experiences failures relatively often, and users receive no compensation, which may be considered an unfair practice. The process stalls, does nothing, and tokens/limits continue to be consumed. No error message is shown.

TL;DR

The issue can be temporarily mitigated by using CTRL+C to stop the process when Claude Code freezes and then resending the prompt.

Guidance

• Verify that the issue is indeed a regression by checking if older versions of Claude Code (if available) exhibit the same behavior.
• Try to identify patterns in when the freezing occurs, such as specific prompts or project types, to potentially isolate the cause.
• Consider reporting the issue to the developers with detailed steps to reproduce and any patterns found, as this could be a bug that needs fixing.
• Since the issue is confirmed to be a regression, checking for any updates to Claude Code that may address this problem is advisable.

Notes

The provided information does not specify the previous working version, which could be crucial for identifying the cause of the regression. Without this information, pinpointing the exact cause or providing a definitive fix is challenging.

Recommendation

Apply workaround: Given the current information, the best course of action seems to be continuing to use CTRL+C to stop the process when it freezes and resending the prompt, while awaiting a potential fix from the developers.