[BUG] Claude Code v2.1.27 gets stuck on the first message, with very high memory usage.
Status Open
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 14 comments · opened Jan 31, 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?
Claude Code v2.1.27 gets stuck on the first message, with very high memory usage.
What Should Happen?
Claude Code v2.1.27 gets stuck on the first message, with very high memory usage.
Error Messages/Logs
Steps to Reproduce
Claude Code v2.1.27 gets stuck on the first message, with very high memory usage.
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
v2.1.27
Platform
AWS Bedrock
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
14 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Definitely some kind of issue going on. Cant switch models, cant do anything.
Same here !
Downgrade to previous version temporarily please
Downgrade:
Disable auto update:
Edit ~/.claude/settings.json
Same for me it gest stuck a lot, and freezes to much
I encountered this issue as well. After extensive troubleshooting, I discovered that deleting all directories such as ~/.claude/session-env and ~/.claude/projects resolved the problem.
fix: https://github.com/anthropics/claude-code/issues/22198#issuecomment-3829158926
That’s a work around.
I did /resume /compact and that worked.
This is the only thing that solves it for me.
ok solved with v2.1.31 for me
2.1.31 did not solve it for me. Still on 2.1.25 as a result.
Are you using Windows?
She solved it for me was a previous comment - a MASSIVE 3 GB JSONL file in .Claude/projects in one of the subprojects.
find . -type f -size +100M -delete
Found the errant file and nuked it and now things are back to normal.