Rank, 14 days: 254 on the Claude Code sheet
2 people reported

All time, since Oct 4.

Config file reset to empty

“On Windows, quitting the Claude desktop app while several Claude Code sessions were running left ~/.claude.json at 0 bytes.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/claude-code/issues/3484/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

~/.claude.json reset to empty on Windows, losing config and trust. File ends up at 0 bytes or near-empty after concurrent writes or quitting with sessions open, wiping MCP servers, workspace trust and onboarding state.

Is this your bug?

File my report
Where
~/.claude.json config
Error text
Failed to parse config file ~/.claude.json (SyntaxError)
Versions
2.1.284 to 2.1.309
Platforms
Windows
How bad
Loses work: code or files lost or damaged.

Not quite your bug?

  1. claude.exe pins one CPU core after watched directory is deleted5 people
  2. Idle sessions keep processes alive7 people
  3. Drive-letter case breaks trust3 people

Original reports2, newest first

  1. Windows: quitting the desktop app mid-save leaves ~/.claude.json at 0 bytes, then config resets to defaults (MCP servers + project trust lost)#106634
  2. ~/.claude.json corruption on Windows from concurrent writes causing data loss and trust reset#99438

Do you work on Claude Code?

Claim its RAP Sheet to see what your users report and answer them in one place.