Feature Request: Auto-rollback alert for critical bugs + Better version management

Problem

Claude Code auto-updated to v2.1.27 which has a critical memory leak bug (ref: #22042), but there was:

• ❌ No warning that this version had known issues
• ❌ No suggestion to rollback to previous stable version
• ❌ No easy way to discover the version was the problem

What Happened (Timeline)

1. 23:00 - Claude Code auto-updated to v2.1.27
2. 23:00-03:00 - Spent 4 HOURS troubleshooting:

• Disabled MCP servers
• Disabled hooks
• Removed Playwright cache
• Uninstalled Chrome
• Cleaned up configs

1. 03:00 - Discovered via web search that v2.1.27 had a memory leak bug
2. 03:05 - Downgraded to v2.1.25 → INSTANT FIX

All troubleshooting was unnecessary - it was just a bad version.

Impact

• 4 hours wasted debugging a known issue
• User frustration and loss of trust in auto-updates
• Unnecessary config changes that needed reverting

Current Situation

Claude Code has:

• ✅ Auto-update mechanism
• ✅ New version notifications
• ❌ NO rollback alerts when versions have critical bugs
• ❌ NO telemetry-based health checks
• ❌ NO easy rollback mechanism

Feature Request

Implement a version health monitoring system:

1. Telemetry Detection: Monitor crash rates, memory leaks, freezes
2. Auto-Alert: When critical bugs are detected, show warning:

⚠️  Claude Code v2.1.27 has known stability issues
→ Recommend downgrading to v2.1.25
→ Run: claude --rollback

1. Easy Rollback: Add claude --rollback command
2. Version Pinning: Add option to disable auto-updates or pin to specific version

Environment

• OS: WSL2 (Ubuntu on Windows 11)
• Buggy Version: v2.1.27
• Working Version: v2.1.25
• Node: v24.13.0

Related Issues

• #22042 (v2.1.27 memory leak bug)

---

TL;DR: Auto-updates are great, but we need auto-rollback alerts when versions have critical bugs. This would save users hours of unnecessary troubleshooting.