[BUG] 2.1.61 wiped out .claude.json - all settings/MCPs gone

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/26437
2. https://github.com/anthropics/claude-code/issues/29056
3. https://github.com/anthropics/claude-code/issues/29153

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

Me and my friend are both having the same issue, corrupted files forcing logouts and unauthenticating mcp servers

All, we've released 2.1.61 which should fix this problem. Please run claude update to get the latest.

This was a disruptive error, so I wanted to share the action items we are going to take:

• We are going to address the underlying race condition that led to processes getting partial reads/EOF. (The hotfix in 2.1.61 only fixes a bug that caused excess writes.)
• We are going to alert on the rate of config corruption events (we had analytics, but they did not trigger paging alarms).
• We are going to add an employee-only feature that exposes excess config writes directly in the UI (this won't be public, but it'll help us catch this category of issue before release).

Thank you so much for your patience here.

All, we've released 2.1.61 which should fix this problem. Please run claude update to get the latest. This was a disruptive error, so I wanted to share the action items we are going to take: We are going to address the underlying race condition that led to processes getting partial reads/EOF. (The hotfix in 2.1.61 only fixes a bug that caused excess writes.) We are going to alert on the rate of config corruption events (we had analytics, but they did not trigger paging alarms). * We are going to add an employee-only feature that exposes excess config writes directly in the UI (this won't be public, but it'll help us catch this category of issue before release). Thank you so much for your patience here.

The update TO 2.1.61 wiped everything out - it is the issue.

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.