[FEATURE] A LTS release

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

While I love new features just live anyone else, I'm stuck on the v2.1.2 because everything beyond that hangs constantly. When that happens tasks get partially done and we lose continuity after the restarting and the agents end up trashing the code base in confusion.

Unfortunately this version has a nasty memory leak which causes me to have to completely shut down my terminal to clear it. So this version is not a good solution, we just have a hacky workaround that still runs into major problems when the terminal grinds to a halt after the memory balloons up 100-1000 times.

Claude Code is not an experiment in my team it's become central to our workflow. When a major bug doesn't get fixed it destroys our productivity. We need a LTS version that we can pin to so that we aren't always at risk of new versions breaking blocking our ability to use the product.

While I love getting new functionality, I as the technology leader can't take on the risk of new versions breaking and losing productivity across the entire team. These last round of bugs has caused us to lose at least 1 weeks worth of productivity and caused numerous cases of rework and code cleanups.

Proposed Solution

I would like to recommend that an LTS version be released. Put a freeze on new features until the biggest blocking bugs have been corrected. There are numerous breaking bugs in the issues that are blocking people from using the product.

Treat this like an Enterprise product where teams can choose to be in the test group (latest branch) or the LTS branch for stability.

Alternative Solutions

As of now my best alternative solution is to pay for a different codegen service but I would prefer to use Claude is the best quality models for our use case.

Priority

Critical - Blocking my work

Feature Category

Performance and speed

Use Case Example

Use case would be

CTO/Director of Engineering/Lead Engineer standardizes the team on LTS version to ensure team productivity is predictable.
Once new LTS versions are released they will be tested by pilot team and once stability and new functionality is understood the LTS is certified and formally approved for the team to migrate to new version.

Additional Context

_No response_