[Bug] Claude Code CLI performance degradation after sustained usage
Bug Description
Subject: Severe performance degradation in Claude Code CLI after short usage
Hello Anthropic Team,
I’d like to report a recurring performance issue I’ve been experiencing with Claude Code (CLI) over the last weeks.
After a short period of usage, the CLI becomes extremely slow to respond. The degradation is progressive and eventually makes the tool barely usable. This happens consistently even in relatively small projects.
To rule out local issues, I’ve already tried the following without success:
- Clearing CLI cache
- Deleting local session/state files
- Restarting the CLI
- Fresh terminal sessions
- Verifying no abnormal system resource constraints
Despite this, the slowdown persists once Claude Code has been used for a while, which suggests a possible issue related to:
- Session accumulation
- Memory leaks
- Context handling or state growth over time
- Background processes not being released correctly
The initial experience is fast and solid, but performance degrades sharply after continued interaction, which significantly impacts productivity—especially when using the CLI as part of an iterative development workflow.
I’m sharing this as constructive feedback in case it aligns with any known issues or helps prioritize investigation on the CLI performance side. If there are recommended diagnostics, flags, or logs I can provide, I’d be happy to help.
Thanks for the work you’re doing, and I hope this feedback is useful.
Best regards,
Roberto Ramírez
Environment Info
- Platform: darwin
- Terminal: Apple_Terminal
- Version: 2.1.5
- Feedback ID: 547badd0-bf97-4b1d-a3ea-afb065194b65
Errors
[]This issue has 8 comments on GitHub. Read the full discussion on GitHub ↗