"One-time reset" in Settings → Usage deleted all chat/session history, not just usage data

Status Fixed / completed
Maintainer reply None cached
Activity 2 comments · opened Sep 28, 2026 · closed Sep 28, 2026

Preflight Checklist

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

What's Wrong?

Severity: Critical — data loss

Environment:

Platform: macOS (Darwin 27.0.0)
App: Claude Code desktop app
Date/time of incident: 2026-09-28

Summary:
Accepted a "one-time reset" option located under Settings → Usage. Expected it to reset usage/billing statistics only. Instead, it deleted all session/chat history — dozens of conversations — with no option to undo or recover them.

Steps to reproduce:

Open Claude Code desktop app.
Navigate to Settings → Usage.
Accept/confirm the "one-time reset" option offered there.
Check session list (sidebar / session history).

Actual behavior:
All prior chat sessions (dozens) disappeared immediately after confirming the reset. Confirmed via the session list API (list_sessions, including archived) — zero sessions returned, active or archived. No recovery/undo option was presented.

Impact:
Total loss of chat history containing ongoing work. No warning that this action was irreversible or that it would affect anything beyond usage data.

Investigate whether affected users' session data is recoverable server-side.
Fix the reset flow to either (a) not delete session history at all, or (b) clearly warn users beforehand and require distinct confirmation for data-destructive scope.

What Should Happen?

A usage/stats reset should only clear usage or billing counters, and should not delete conversation history. At minimum, a destructive action like this should carry an explicit warning ("This will permanently delete X chats") and require separate confirmation.

Error Messages/Logs

All prior chat sessions (dozens) disappeared immediately after confirming the reset. Confirmed via the session list API (list_sessions, including archived) — zero sessions returned, active or archived. No recovery/undo option was presented.

Steps to Reproduce

Investigate whether affected users' session data is recoverable server-side.
Fix the reset flow to either (a) not delete session history at all, or (b) clearly warn users beforehand and require distinct confirmation for data-destructive scope.

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.9939.2

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗