[DOCS] No release notes for v2.0.0

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/715
2. https://github.com/anthropics/claude-code/issues/463
3. https://github.com/anthropics/claude-code/issues/5759

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

I also noticed that it seems to have updated to v2 automatically, which feels unusual — all prior updates I can remember required a manual version bump. The new version also looks visually different, but I couldn’t find anything in the changelog or announcements about the update.

Given the timing with some recent npm supply chain attacks, I honestly wondered for a moment if this might be something malicious. Would be great to have clarification on whether the auto-update was intentional and if there are release notes we can reference.

The changelog is now updated: https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md

The changelog is now updated: https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md

Re: v2.0.0 Release - Critical .claude.json Architecture Issue Remains Unaddressed

Team Anthropic,

I've reviewed the v2.0.0 changelog with great anticipation, hoping that a major version release would finally address the critical architectural issues documented in #7243, #5024, #1449, and #6394. Unfortunately, I must express my profound disappointment.

Version 2.0.0 Analysis

Your major release includes:

• Native VS Code extension
• UI refresh ("fresh coat of paint")
• /rewind command for conversation rollback
• /usage command for plan limits
• Tab toggle for thinking mode
• Ctrl-R for history search

Notably absent: Any mention of resolving the .claude.json architectural failure.

The Severity of This Oversight

This is not a minor bug - it's a fundamental violation of software architecture principles that has been impacting production users for over 8 months:

1. Performance Degradation: Users report 65MB+ config files causing 30+ second startup times
2. Data Integrity: Multiple reports of corruption (#3117, #2593, #6181)
3. Resource Exhaustion: 72+ duplicate MCP processes spawning
4. Security Implications: Forcing sensitive conversation data into version control

Industry Context

A major version (2.0.0) traditionally signals breaking changes and architectural improvements. The software engineering community expects:

• Resolution of technical debt
• Architectural refinements
• Performance optimizations
• Breaking changes that improve long-term maintainability

Instead, v2.0.0 delivers cosmetic improvements while ignoring a critical architectural flaw that violates the Single Responsibility Principle - a concept taught in CS101.

Professional Assessment

The decision to ship v2.0.0 without addressing this issue suggests either:

1. A fundamental misunderstanding of the problem's severity
2. Technical limitations preventing proper implementation
3. Prioritization decisions that favor features over stability

Any of these scenarios is concerning for an AI coding assistant that markets itself as enterprise-ready.

Proposed Path Forward

As a member of the professional development community, I strongly urge:

1. Immediate Acknowledgment: Public recognition of this architectural debt
2. Roadmap Inclusion: Clear timeline for resolution (v2.1.0?)
3. Proper Implementation: Separation of configuration and data using appropriate storage mechanisms (SQLite for history, JSON for config)
4. Community Engagement: Many of us have offered solutions and workarounds

Competitive Landscape

While Claude Code adds "fresh paint," your competitors are solving fundamental problems:

• DeepSeek's upcoming agent (Bloomberg, Sept 2025)
• Microsoft Copilot Workspace's stable architecture
• Open-source alternatives with proper data management

Conclusion

The professional development community has been exceptionally patient. We've provided detailed technical analysis, reproducible test cases, and even architectural solutions. What we need now is not more UI polish, but fundamental engineering rigor.

A major version release without addressing known critical architectural issues undermines confidence in the product's technical leadership and long-term viability.

I urge you to prioritize this issue immediately. The community is ready to support a proper solution, but we need commitment from Anthropic's engineering leadership.

Respectfully but urgently,
Andrey Kolkov
Author of #7243

cc: @anthropic-engineering-leadership @claude-code-maintainers

---

Note to fellow developers: Please 👍 this comment if you're experiencing similar issues. Let's ensure our collective voice is heard.

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.