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

[privacyguy123]

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

Really? I am fucking FURIOUS. I see NO backup for this file.

What Should Happen?

I should open Claude back where I left off after update.

Error Messages/Logs

None.

Steps to Reproduce

1. Update to 2.1.61
2. Everything wiped
3. Cool

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.59

Claude Code Version

2.1.61

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

No response

[github-actions]

Found 3 possible duplicate issues:

1. 2.1.45 update silently resets MCP configs, user ID, and project trust dialogs #26437
2. Windows: .claude.json falsely detected as corrupted on exit, wiping onboarding state #29056
3. Windows + OneDrive: .claude.json corruption cascade from concurrent writes #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

[braasdas]

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

[shawnm-anthropic]

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.

[privacyguy123]

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.

[github-actions]

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.